adamm/git-importer
1
0
Fork 1
forked from importers/git-importer
Code Pull Requests Activity
9554fea7e1
git-importer/tests/fixtures/zsh-data.yaml

31929 lines
830 KiB
YAML
Raw Normal View History

Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
revisions:
- broken: false
comment: ''
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2007-01-16 00:46:06
expanded_srcmd5: 67b911ff090458a9686081fb6f248965
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
- md5: e73e3324c45852959171975f8a77ee97
mtime: 1161591945
name: zsh.changes
size: 10842
- md5: 52ab752f4e84df9fa5bf86611b36e242
mtime: 1161591946
name: zsh.spec
size: 9713
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 1c65b8438b9313624487ff6a385ae64e
mtime: 1142381840
name: zshrc
size: 6825
files_hash: 5dc439fa0777ccb8e1b7e4c6f3b7e65e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 1.0
unexpanded_srcmd5: 67b911ff090458a9686081fb6f248965
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: unknown
- broken: false
comment: ''
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2007-03-30 16:36:08
expanded_srcmd5: 01ba90b334e80918c9d7dc9647495d11
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
- md5: 5887da8a9ae75468c41b837426f00afd
mtime: 1175265368
name: zsh.changes
size: 10997
- md5: 02d60b4e02556c5717d3e824a22ee672
mtime: 1175265368
name: zsh.spec
size: 9815
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 1c65b8438b9313624487ff6a385ae64e
mtime: 1142381840
name: zshrc
size: 6825
files_hash: d68d770fbdcf221207705803048aff88
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 2.0
unexpanded_srcmd5: 01ba90b334e80918c9d7dc9647495d11
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: unknown
- broken: false
comment: ''
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2007-07-04 23:21:41
expanded_srcmd5: 010207cf36943791f78149dc4c4001e6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: 839c1f8e922615691ad7824e504f118f
mtime: 1183561483
name: zsh.changes
size: 11297
- md5: dcd0fb0849b7f36c4d0270d8ab927312
mtime: 1183584100
name: zsh.spec
size: 10137
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: b653d60e25094de2a45b8ef74d589736
mtime: 1183561484
name: zshrc
size: 6814
files_hash: 397ff834c6df9037ddfe327723285c83
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 3.0
unexpanded_srcmd5: 010207cf36943791f78149dc4c4001e6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: unknown
- broken: false
comment: ''
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2007-12-04 00:03:34
expanded_srcmd5: 2e9af25c504d0cebf9dd990efea29a70
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: 7d672299059b208075aee807c5753efe
mtime: 1196723013
name: zsh.changes
size: 11745
- md5: 5b01476139594dbdbf35a3944758569c
mtime: 1196723013
name: zsh.spec
size: 10563
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 24c9eed4774f1224b85c30331a5e16b1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 4.0
unexpanded_srcmd5: 2e9af25c504d0cebf9dd990efea29a70
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: unknown
- broken: false
comment: ''
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2008-03-21 05:17:09
expanded_srcmd5: 8231c715d598ad282680f3d9f6845acd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0370558bcd27b6aeea54a0dc6a215b57
mtime: 1206073029
name: zsh-4.3.4.diff
size: 9298
- md5: 2edea09b823ffa7528dbd447485630c9
mtime: 1206073029
name: zsh-4.3.5-doc.tar.bz2
size: 2463496
- md5: db0d4b71da8e5877fa1e29d4cea38b8c
mtime: 1206073029
name: zsh-4.3.5.tar.bz2
size: 2513384
- md5: 24788c563ae8868b1a5accb384aef62b
mtime: 1206073029
name: zsh.changes
size: 12641
- md5: 1b00c88e9620bbcc702a72915c1e461b
mtime: 1206073029
name: zsh.spec
size: 11186
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 1d020dc05f060aefd1f2885a2569ff57
package: zsh
project: openSUSE:Factory
rev: 5.0
unexpanded_srcmd5: 8231c715d598ad282680f3d9f6845acd
userid: unknown
- broken: false
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
comment: ''
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2008-03-28 05:11:23
expanded_srcmd5: 9f117ce236894df3740a5680da95b129
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0370558bcd27b6aeea54a0dc6a215b57
mtime: 1206073029
name: zsh-4.3.4.diff
size: 9298
- md5: 2edea09b823ffa7528dbd447485630c9
mtime: 1206073029
name: zsh-4.3.5-doc.tar.bz2
size: 2463496
- md5: db0d4b71da8e5877fa1e29d4cea38b8c
mtime: 1206073029
name: zsh-4.3.5.tar.bz2
size: 2513384
- md5: e4d9889675426d62847316d427760867
mtime: 1206677483
name: zsh.changes
size: 12809
- md5: 2a3c923e161a4e519d9c77bbde6427f7
mtime: 1206677483
name: zsh.spec
size: 11418
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 9b28d3a11cd900316173740aa4537737
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 6.0
unexpanded_srcmd5: 9f117ce236894df3740a5680da95b129
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: unknown
- broken: false
comment: ''
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2008-04-04 01:49:28
expanded_srcmd5: 4469e0b0ae1accfa29df8f2ac29e631b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0370558bcd27b6aeea54a0dc6a215b57
mtime: 1206073029
name: zsh-4.3.4.diff
size: 9298
- md5: cab29228a90f58b1431a66ab24a0a0c2
mtime: 1207266567
name: zsh-4.3.6-doc.tar.bz2
size: 2473544
- md5: 16f399af1081ad3c303a794c9c7dc47e
mtime: 1207266568
name: zsh-4.3.6.tar.bz2
size: 2527972
- md5: b26796003e008dae88860be284695488
mtime: 1207266568
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 13344
- md5: 50accfafd3cf3b1761d9030987fb99d8
mtime: 1207266568
name: zsh.spec
size: 11865
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 1d68dbe4146fec195e55a16fa7abd2e3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 7.0
unexpanded_srcmd5: 4469e0b0ae1accfa29df8f2ac29e631b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: unknown
- broken: false
comment: ''
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2008-06-23 04:13:52
expanded_srcmd5: e9f54979d62ad4b270630491989d3e58
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0370558bcd27b6aeea54a0dc6a215b57
mtime: 1206073029
name: zsh-4.3.4.diff
size: 9298
- md5: cab29228a90f58b1431a66ab24a0a0c2
mtime: 1207266567
name: zsh-4.3.6-doc.tar.bz2
size: 2473544
- md5: 16f399af1081ad3c303a794c9c7dc47e
mtime: 1207266568
name: zsh-4.3.6.tar.bz2
size: 2527972
- md5: 5fd32cad7da00144744857e36eef396a
mtime: 1214187232
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 13489
- md5: 3d99d70049862bf83e8a4f70e347bd04
mtime: 1214187232
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 11938
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 325a2c0ef609552988e0fd2b43dc24f2
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 8.0
unexpanded_srcmd5: e9f54979d62ad4b270630491989d3e58
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: unknown
- broken: false
comment: ''
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2008-09-24 00:56:32
expanded_srcmd5: 15240d9f2bfbf12f225e724395d399c9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0370558bcd27b6aeea54a0dc6a215b57
mtime: 1206073029
name: zsh-4.3.4.diff
size: 9298
- md5: cab29228a90f58b1431a66ab24a0a0c2
mtime: 1207266567
name: zsh-4.3.6-doc.tar.bz2
size: 2473544
- md5: 16f399af1081ad3c303a794c9c7dc47e
mtime: 1207266568
name: zsh-4.3.6.tar.bz2
size: 2527972
- md5: 3de43c7d7ecb74247c4cea9932075e67
mtime: 1222210592
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 13658
- md5: 487c422cad62e0394588c90a7116c5e6
mtime: 1222210592
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 12470
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: c42661a9c9f4d0084783edeaec03fb48
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 9.0
unexpanded_srcmd5: 15240d9f2bfbf12f225e724395d399c9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: unknown
- broken: false
comment: ''
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2008-10-06 16:53:23
expanded_srcmd5: e8840530bdfd9cc82be7200609a6fe81
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0370558bcd27b6aeea54a0dc6a215b57
mtime: 1206073029
name: zsh-4.3.4.diff
size: 9298
- md5: cab29228a90f58b1431a66ab24a0a0c2
mtime: 1207266567
name: zsh-4.3.6-doc.tar.bz2
size: 2473544
- md5: 16f399af1081ad3c303a794c9c7dc47e
mtime: 1207266568
name: zsh-4.3.6.tar.bz2
size: 2527972
- md5: 001e3930a47e917ae48d1f41642142b0
mtime: 1223304803
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 13842
- md5: a553b2103e07e6d54df4cddfe48ffbab
mtime: 1223304803
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 12570
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: 866f99334737a0585e482a38984f8398
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 10.0
unexpanded_srcmd5: e8840530bdfd9cc82be7200609a6fe81
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: unknown
- broken: false
comment: ''
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2009-05-25 17:28:59
expanded_srcmd5: 49595d834a25c708402a4fdc2c5141c3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0370558bcd27b6aeea54a0dc6a215b57
mtime: 1206073029
name: zsh-4.3.4.diff
size: 9298
- md5: cab29228a90f58b1431a66ab24a0a0c2
mtime: 1207266567
name: zsh-4.3.6-doc.tar.bz2
size: 2473544
- md5: 16f399af1081ad3c303a794c9c7dc47e
mtime: 1207266568
name: zsh-4.3.6.tar.bz2
size: 2527972
- md5: 7131dcf1e0848eadb6466da7558e0d6a
mtime: 1240575342
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 14029
- md5: d8836d243949cf13dd574d8b4b273747
mtime: 1243265339
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 12709
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: 1b5f336a1ae38528a7dd3bad24f9a117
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 11.0
unexpanded_srcmd5: 49595d834a25c708402a4fdc2c5141c3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: unknown
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 'Copy from shells/zsh based on submit request 18109 from user hennevogel
'
commit_time: 2009-08-19 00:11:24
expanded_srcmd5: 84c5477e4491cfb21b86893c214fb621
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c8e1db4ea4393ffdec4a36eb052fa354
mtime: 1250592645
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 15596
- md5: a431a22b103004ec80d92abc8f3080bb
mtime: 1250633484
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 5181
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b653d60e25094de2a45b8ef74d589736
mtime: 1183561484
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6814
files_hash: cbc154833f9bdb7d2d9b04fe1b63ecb3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: hennevogel
number: 18109
source_package: zsh
source_project: shells
source_rev: '30'
state: accepted
type: submit
rev: 12.0
unexpanded_srcmd5: 84c5477e4491cfb21b86893c214fb621
userid: autobuild
- broken: false
comment: 'Copy from shells/zsh based on submit request 18351 from user hennevogel
'
commit_time: 2009-08-21 18:41:30
expanded_srcmd5: 31973639ea9530e63afe686a1f72061e
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: b84ef89cabc22933fcd33a677cd2cb8f
mtime: 1250765564
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 15776
- md5: 11040c40cb2b37049b33d4e395cb3c06
mtime: 1250872890
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 5181
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: c1e181638f1088544b5fa395704558ec
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: hennevogel
number: 18351
source_package: zsh
source_project: shells
source_rev: '33'
state: accepted
type: submit
rev: 13.0
unexpanded_srcmd5: 31973639ea9530e63afe686a1f72061e
userid: autobuild
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 'Copy from shells/zsh based on submit request 22308 from user coolo
'
commit_time: 2009-10-13 17:27:29
expanded_srcmd5: dcfccc1762f4fcce3c3857a13c754e4b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: a0f91c040db93d6a49e8d85ded5e4dfd
mtime: 1255019009
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 15922
- md5: 26336ee303cb6d45a1ca215383c7fd05
mtime: 1255447649
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: 18d5fc82295b89ec951ed46159c0b3cd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: coolo
number: 22308
source_package: zsh
source_project: shells
source_rev: '35'
state: accepted
type: submit
rev: 14.0
unexpanded_srcmd5: dcfccc1762f4fcce3c3857a13c754e4b
userid: autobuild
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 'Copy from shells/zsh based on submit request 22308 from user coolo
'
commit_time: 2009-10-13 17:27:29
expanded_srcmd5: dcfccc1762f4fcce3c3857a13c754e4b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: a0f91c040db93d6a49e8d85ded5e4dfd
mtime: 1255019009
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 15922
- md5: 26336ee303cb6d45a1ca215383c7fd05
mtime: 1255447649
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: 18d5fc82295b89ec951ed46159c0b3cd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: coolo
number: 22308
source_package: zsh
source_project: shells
source_rev: '35'
state: accepted
type: submit
rev: 15.0
unexpanded_srcmd5: dcfccc1762f4fcce3c3857a13c754e4b
userid: autobuild
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 'Copy from shells/zsh based on submit request 26620 from user coolo
'
commit_time: 2009-12-16 13:38:29
expanded_srcmd5: 3f6bf0912177c61b3e4ae57ccf303833
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: 1d2c10dfbf731be6a2702062c0a2a568
mtime: 1259777956
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 16076
- md5: fa3228826fb810f863c1654535e37291
mtime: 1260967109
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: 5cbb75a7f4cd6050f4b697f0cc88ce5c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: coolo
number: 26620
source_package: zsh
source_project: shells
source_rev: null
state: accepted
type: submit
rev: 16.0
unexpanded_srcmd5: 3f6bf0912177c61b3e4ae57ccf303833
userid: autobuild
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 'Copy from shells/zsh based on submit request 34678 from user hennevogel
'
commit_time: 2010-03-12 17:37:41
expanded_srcmd5: c7e5c9793ea863b9c313c3d78b7356a8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c91d2e28a2ea0da32d33342a2db37639
mtime: 1268150089
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 16437
- md5: 23a0b81db63eade0296ad7e0dbb3b196
mtime: 1268411861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: 2c5a1c06b358a6b3352811a05ef026b0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: hennevogel
number: 34678
source_package: zsh
source_project: shells
source_rev: '40'
state: accepted
type: submit
rev: 17.0
unexpanded_srcmd5: c7e5c9793ea863b9c313c3d78b7356a8
userid: autobuild
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: ''
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2010-03-18 16:40:26
expanded_srcmd5: 437074d6188a7dbfba05ada6bd049b0d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c91d2e28a2ea0da32d33342a2db37639
mtime: 1268150089
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 16437
- md5: 23a0b81db63eade0296ad7e0dbb3b196
mtime: 1268411861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: e2edeca864a6b90c3844dbc7d5dd060c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 18.0
unexpanded_srcmd5: 437074d6188a7dbfba05ada6bd049b0d
userid: autobuild
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: release number sync
commit_time: 2010-07-09 11:23:19
expanded_srcmd5: 437074d6188a7dbfba05ada6bd049b0d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c91d2e28a2ea0da32d33342a2db37639
mtime: 1268150089
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 16437
- md5: 23a0b81db63eade0296ad7e0dbb3b196
mtime: 1268411861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: e2edeca864a6b90c3844dbc7d5dd060c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 19.0
unexpanded_srcmd5: 437074d6188a7dbfba05ada6bd049b0d
userid: autobuild
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: release number sync
commit_time: 2010-07-09 14:30:34
expanded_srcmd5: 437074d6188a7dbfba05ada6bd049b0d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c91d2e28a2ea0da32d33342a2db37639
mtime: 1268150089
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 16437
- md5: 23a0b81db63eade0296ad7e0dbb3b196
mtime: 1268411861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: e2edeca864a6b90c3844dbc7d5dd060c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 20.0
unexpanded_srcmd5: 437074d6188a7dbfba05ada6bd049b0d
userid: autobuild
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 11.4 source split
commit_time: 2011-02-17 12:18:45
expanded_srcmd5: 437074d6188a7dbfba05ada6bd049b0d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c91d2e28a2ea0da32d33342a2db37639
mtime: 1268150089
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 16437
- md5: 23a0b81db63eade0296ad7e0dbb3b196
mtime: 1268411861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: e2edeca864a6b90c3844dbc7d5dd060c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 21.0
unexpanded_srcmd5: 437074d6188a7dbfba05ada6bd049b0d
userid: autobuild
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 'Accepted submit request 63473 from user coolo
'
commit_time: 2011-03-07 15:13:58
expanded_srcmd5: 2e2ba50c910ad535d6629324101aaffb
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: _osc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 44c92fe036a05ed9da5cf541e4765ad0
mtime: 1292857805
name: _service:download_url:zsh-4.3.11-doc.tar.bz2
size: 2687527
- md5: 3225c7f53b69f395e95723585d6785ed
mtime: 1292861216
name: _service:download_url:zsh-4.3.11.tar.bz2
size: 2868429
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 3c4c48fa72e6d5051d6d64c1f4f8c099
mtime: 1293588990
name: zsh.changes
size: 16824
- md5: 67ed7e6957ae59ab39233035c35d1000
mtime: 1293588991
name: zsh.spec
size: 5205
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: 0beef51012acb75aae88b2f1c230c99b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: coolo
number: 63473
source_package: zsh
source_project: shells
source_rev: null
state: accepted
type: submit
rev: 22.0
unexpanded_srcmd5: 2e2ba50c910ad535d6629324101aaffb
userid: saschpe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 'Autobuild autoformatter for 63473
'
commit_time: 2011-03-07 15:14:09
expanded_srcmd5: a8a8bb74ba243141c98b07fed946a2fd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: _osc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 44c92fe036a05ed9da5cf541e4765ad0
mtime: 1292857805
name: _service:download_url:zsh-4.3.11-doc.tar.bz2
size: 2687527
- md5: 3225c7f53b69f395e95723585d6785ed
mtime: 1292861216
name: _service:download_url:zsh-4.3.11.tar.bz2
size: 2868429
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 3c4c48fa72e6d5051d6d64c1f4f8c099
mtime: 1293588990
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 16824
- md5: 35d43f1d73ff413cd02c4db48ca10c46
mtime: 1299507249
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 5187
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: b8ee837e60f0d18c01dbd3ddb7df13ce
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 23.0
unexpanded_srcmd5: a8a8bb74ba243141c98b07fed946a2fd
userid: saschpe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 'Accepted submit request 64202 from user namtrac
'
commit_time: 2011-03-16 11:21:24
expanded_srcmd5: a8f52d7cfa173e5fd951c77e5e31528e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: _osc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 44c92fe036a05ed9da5cf541e4765ad0
mtime: 1292857805
name: _service:download_url:zsh-4.3.11-doc.tar.bz2
size: 2687527
- md5: 3225c7f53b69f395e95723585d6785ed
mtime: 1292861216
name: _service:download_url:zsh-4.3.11.tar.bz2
size: 2868429
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0572141ef2a2c1239a8613f7600e9d5d
mtime: 1300198323
name: subst-crash.patch
size: 1100
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 5acf2fde717b866ad409b0070c0a4950
mtime: 1300198326
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 16972
- md5: 56893f45631ff3f8b0684783e5e53e28
mtime: 1300198329
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 5233
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: 3112f8413e243d712ecf3a76b429dbc0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 64202
source_package: zsh
source_project: shells
source_rev: null
state: accepted
type: submit
rev: 24.0
unexpanded_srcmd5: a8f52d7cfa173e5fd951c77e5e31528e
userid: saschpe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 'Autobuild autoformatter for 64202
'
commit_time: 2011-03-16 11:21:38
expanded_srcmd5: 0263399b08bb63c36702bd4edfacbad6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: _osc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 44c92fe036a05ed9da5cf541e4765ad0
mtime: 1292857805
name: _service:download_url:zsh-4.3.11-doc.tar.bz2
size: 2687527
- md5: 3225c7f53b69f395e95723585d6785ed
mtime: 1292861216
name: _service:download_url:zsh-4.3.11.tar.bz2
size: 2868429
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0572141ef2a2c1239a8613f7600e9d5d
mtime: 1300198323
name: subst-crash.patch
size: 1100
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh-cleanup.patch
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1081
- md5: 5acf2fde717b866ad409b0070c0a4950
mtime: 1300198326
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 16972
- md5: 4c9fa541dccbea30e2954d4af2c068bf
mtime: 1300270898
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 5233
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: d9699f7407eca48bb9ef9b199767dcdd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 25.0
unexpanded_srcmd5: 0263399b08bb63c36702bd4edfacbad6
userid: saschpe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Update to 4.3.11 dev 2 release
- Enable and fix make check
- Disable zsh debug
'
commit_time: 2011-04-29 09:15:29
expanded_srcmd5: 893846821ee39912dd58d590139b2e33
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: _osc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 4146
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: 04b864452ce11f5432b452e37220ed99
mtime: 1303410159
name: zsh-4.3.11-disable-c02cond-test.patch
size: 409
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: e3f12a27e6a4630f3ad8682b706a6b54
mtime: 1303407548
name: zsh-4.3.11-fix-a01grammar.patch
size: 386
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh-cleanup.patch
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1081
- md5: e7ca2b955593216ff1ce9937318b83e5
mtime: 1303832781
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 17452
- md5: 92a669ef8c7b9577048c51f250b2d54c
mtime: 1303409484
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 4658
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: 587abcb76f5eb1274f152ad63f77c3e7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 68403
source_package: zsh
source_project: shells
source_rev: '66'
state: accepted
type: submit
rev: 26.0
unexpanded_srcmd5: 893846821ee39912dd58d590139b2e33
userid: saschpe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 'Autobuild autoformatter for 68403
'
commit_time: 2011-04-29 09:15:42
expanded_srcmd5: 41efdc7ab019257a66f9d5b78433c3bd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: _osc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 4146
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: 04b864452ce11f5432b452e37220ed99
mtime: 1303410159
name: zsh-4.3.11-disable-c02cond-test.patch
size: 409
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: e3f12a27e6a4630f3ad8682b706a6b54
mtime: 1303407548
name: zsh-4.3.11-fix-a01grammar.patch
size: 386
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh-cleanup.patch
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1081
- md5: e7ca2b955593216ff1ce9937318b83e5
mtime: 1303832781
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 17452
- md5: 467b540e277d60f820f78c083bd299f1
mtime: 1304061342
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 4672
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: 0aaf34df42f0f8ac44ba191256492684
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 27.0
unexpanded_srcmd5: 41efdc7ab019257a66f9d5b78433c3bd
userid: saschpe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Update to final 4.3.12 release, all openSUSE specific completions are now
upstream!
commit_time: 2011-06-06 13:16:02
expanded_srcmd5: 38ab3c2de1cd10bb1ed584a63cbec9f4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: 4869467391046af289e6cf0acfc4be1d
mtime: 1306935383
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 17660
- md5: e2c3b46c96f6a334cac10452babd0914
mtime: 1306164758
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 3731
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 963a9d04d6a12596fdac68d85449547e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 72437
source_package: zsh
source_project: shells
source_rev: '69'
state: accepted
type: submit
rev: 28.0
unexpanded_srcmd5: 38ab3c2de1cd10bb1ed584a63cbec9f4
userid: saschpe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Add zsh-kill-suspended-job.patch: fix killing suspended jobs
- Add zsh-findproc.patch: fix findproc() to find stopped jobs'
commit_time: 2011-06-20 11:00:45
expanded_srcmd5: 31c3e4ef2e0ccbd1997668322453efe7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 53450d7cc95c0b906ee900cabb9934ac
mtime: 1308318146
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 17906
- md5: a66d9fc153c15122a6c390fe67fdc2cc
mtime: 1308318146
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 4089
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
files_hash: 13cdb1e0c6f7b2cb361254b4e9310c05
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 74050
source_package: zsh
source_project: shells
source_rev: '71'
state: accepted
type: submit
rev: 29.0
unexpanded_srcmd5: 31c3e4ef2e0ccbd1997668322453efe7
userid: saschpe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 'Autobuild autoformatter for 74050
'
commit_time: 2011-06-20 11:00:57
expanded_srcmd5: ee049a8385fcce3f70f1ed81d1d84e59
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 53450d7cc95c0b906ee900cabb9934ac
mtime: 1308318146
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 17906
- md5: 57f7c2bc180e86c11399a4cf1f7c9f4a
mtime: 1308560457
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 4089
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 2cd199f053e43c33c01e830e43a7f24a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 30.0
unexpanded_srcmd5: ee049a8385fcce3f70f1ed81d1d84e59
userid: saschpe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Enable pcre module \n- Build against ncurses6w instead of plain old\
\ ncurses5 (forwarded request 77731 from elvigia)"
commit_time: 2011-08-03 10:57:44
expanded_srcmd5: 229308494a99d4cb13762e081bb29288
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 13fb916523341afc7a37232ee386d115
mtime: 1312240671
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 18506
- md5: 9de5cb3d353fbe5d882984dd620420b4
mtime: 1312240672
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8151
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 3bae3852ddedc66ed759ae5392001ac0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 77747
source_package: zsh
source_project: shells
source_rev: '75'
state: accepted
type: submit
rev: 31.0
unexpanded_srcmd5: 229308494a99d4cb13762e081bb29288
userid: saschpe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 'Autobuild autoformatter for 77747
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
'
commit_time: 2011-08-03 10:57:54
expanded_srcmd5: 273ce0c34c4ebf88ca7d70328ed32583
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 13fb916523341afc7a37232ee386d115
mtime: 1312240671
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 18506
- md5: 6c5616776cb2bb6923054fe425de691c
mtime: 1312361874
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8151
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 478eb7f1233ae6fef2e802733316ca10
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 32.0
unexpanded_srcmd5: 273ce0c34c4ebf88ca7d70328ed32583
userid: saschpe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2011-10-21 09:37:28
expanded_srcmd5: 273ce0c34c4ebf88ca7d70328ed32583
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 13fb916523341afc7a37232ee386d115
mtime: 1312240671
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 18506
- md5: 6c5616776cb2bb6923054fe425de691c
mtime: 1312361874
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8151
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 478eb7f1233ae6fef2e802733316ca10
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 33.0
unexpanded_srcmd5: 273ce0c34c4ebf88ca7d70328ed32583
userid: adrianSuSE
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Add custom completion support via /etc/zsh_completion.d \n- Fix build\
\ with new ncurses library"
commit_time: 2011-11-25 11:21:37
expanded_srcmd5: 143b2bdfad0b74102a9135bf5e41f1c5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 83ae5eda450d00467008f00eafc1f92d
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 18720
- md5: 109efda15270af5065870938793d9262
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8370
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: d2dea0913a3375e4537a985ba7348f2a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 93396
source_package: zsh
source_project: shells
source_rev: '77'
state: accepted
type: submit
rev: 34.0
unexpanded_srcmd5: 143b2bdfad0b74102a9135bf5e41f1c5
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "I fixed the changelog to say 4._3_.13 not 4.2, sorry!\n\n- Update to zsh\
\ 4.3.13\n * There are no significant feature changes to the shell itself, \n\
\ although many bug fixes and improvements to functions.\n * See included\
\ ChangeLog for details\n- Drop zsh-4.3.12-ksh-emulation-syntax-checking.patch,\
\ \n fixed upstream\n\n- Cleanup spec file\n- Make /bin/zsh a symlink to /usr/bin/zsh\n\
\n- Update to 4.3.12-test3\n * See included ChangeLog for details\n- Drop zsh-findproc.patch\
\ and zsh-kill-suspended-job.patch, fixed\n upstream."
commit_time: 2011-12-01 17:39:37
expanded_srcmd5: 56d414f65d09919944c93940758b993f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 5b95e276b6344776cffa01edebfe606d
mtime: 1322690000
name: zsh-4.3.13.tar.bz2
size: 2964918
- md5: 90bde02af9623ba6c42b8068f074b933
mtime: 1322734553
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 19539
- md5: 6c1808fce1765816716c2535a5c45227
mtime: 1322690000
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7698
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: a0c04870d23cf557e3c5e5c51144a462
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 94661
source_package: zsh
source_project: shells
source_rev: '84'
state: accepted
type: submit
rev: 35.0
unexpanded_srcmd5: 56d414f65d09919944c93940758b993f
userid: coolo
- broken: false
comment: "- Update to zsh 4.3.15\n * Fix POSIX compatibility\n\n- Update to zsh\
\ 4.3.14\n * Drop 74eed99c312de05e19b54ba6b5d37a0aeb4ba713.patch and\n 724fd07a67f135c74eba57e9f25fd342201ec722.patch,\
\ fixed upstream\n * Fix for nanosecond timestamp support\n\n- Fix license to\
\ be MIT, zsh seems to be using the \"Modern\" variant\n of the license text.\n\
- Import git commits 74eed99c312de05e19b54ba6b5d37a0aeb4ba713 and\n 724fd07a67f135c74eba57e9f25fd342201ec722\n\
\ * metafy() added null termination even if buffer was not modifiable\n * Fix\
\ uninitialised memory after lexer realloc"
commit_time: 2012-01-04 07:33:12
expanded_srcmd5: 0e003b396799399336ab501d81f3f1fb
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: 7727cd1dcec15fac64c79f8d1bbd6d86
mtime: 1324373637
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 20455
- md5: 4719270411956b74c52f6324f3915870
mtime: 1324373755
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7513
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 9e48a6012654b6c4e51c516c06649692
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 97159
source_package: zsh
source_project: shells
source_rev: '90'
state: accepted
type: submit
rev: 36.0
unexpanded_srcmd5: 0e003b396799399336ab501d81f3f1fb
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update _osc completion \n\n- Instead of disabling c02cond manually,\
\ add upstream patch to\n automatically disable it on noatime mounted systems."
commit_time: 2012-02-01 10:01:22
expanded_srcmd5: 6975a1abdbf8ef2f2d9f6d317e484233
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: b466c94d21935ad71254e78ef7aa3b5e
mtime: 1324925887
name: osc.patch
size: 1523
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 5d5c8e88ce1631b3337a9a4444c009d9
mtime: 1325328500
name: zsh-4.3.12-fix-c02cond-test.patch
size: 812
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: 551371c36b59aacc511daa3e4902d738
mtime: 1328008081
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 20835
- md5: ce41c88feaa37c268b80dfc615d508c3
mtime: 1328008081
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7622
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: a9debeaf63ecb65a4b2bb790137896d6
package: zsh
project: openSUSE:Factory
request:
creator: namtrac
number: 102187
source_package: zsh
source_project: shells
source_rev: '95'
state: accepted
type: submit
rev: 37.0
unexpanded_srcmd5: 6975a1abdbf8ef2f2d9f6d317e484233
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Enable installation of openSUSE completion functions which are upstream
(forwarded request 103060 from hmacht)
commit_time: 2012-02-08 15:44:17
expanded_srcmd5: faa27c04d4d7fce5bd987d8193b19657
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: b466c94d21935ad71254e78ef7aa3b5e
mtime: 1324925887
name: osc.patch
size: 1523
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 5d5c8e88ce1631b3337a9a4444c009d9
mtime: 1325328500
name: zsh-4.3.12-fix-c02cond-test.patch
size: 812
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: ee16c2674687b8d861106d39ad80488c
mtime: 1328621263
name: zsh-enable-openSUSE-completion-functions.patch
size: 891
- md5: 067fa2bb6e20b1bb5b09d65a358384a6
mtime: 1328626475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21079
- md5: 7f3b3b8001df2167422481c742cb6571
mtime: 1328621263
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7699
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: e0147fc7631c1d01176b60ecfad686dd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 103061
source_package: zsh
source_project: shells
source_rev: '98'
state: accepted
type: submit
rev: 38.0
unexpanded_srcmd5: faa27c04d4d7fce5bd987d8193b19657
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 4.3.17\n * Contains fixes for possible speed regression\
\ introduced \n in 4.3.15 (new option HASH_EXECUTABLES_ONLY)\n * Improvements\
\ to (bash) completion and shell emulation mode \n- Drop all the patches, all\
\ upstream"
commit_time: 2012-02-27 18:39:10
expanded_srcmd5: da7de9f7f438324b959e626abb52764a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: ecb3c5985edec46b0bd0b20bae0f2e36
mtime: 1330334124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21435
- md5: bb19114a83e66b0cbdb6d40a2a7ff0a1
mtime: 1330334124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7519
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: ee45f866cddbb3ea4cc63c334698d923
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 107122
source_package: zsh
source_project: shells
source_rev: '100'
state: accepted
type: submit
rev: 39.0
unexpanded_srcmd5: da7de9f7f438324b959e626abb52764a
userid: coolo
- broken: false
comment: branched from openSUSE:Factory
commit_time: 2012-06-20 11:27:02
expanded_srcmd5: da7de9f7f438324b959e626abb52764a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: ecb3c5985edec46b0bd0b20bae0f2e36
mtime: 1330334124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21435
- md5: bb19114a83e66b0cbdb6d40a2a7ff0a1
mtime: 1330334124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7519
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: ee45f866cddbb3ea4cc63c334698d923
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 40.0
unexpanded_srcmd5: da7de9f7f438324b959e626abb52764a
userid: adrianSuSE
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- buildrequire makeinfo to fix build (forwarded request 128306 from coolo)'
commit_time: 2012-07-20 10:26:00
expanded_srcmd5: b84c0e53e8110d924040a7b8c84b431f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: 182a172cdfd776eb436fabe5b0b63b9c
mtime: 1342684709
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21588
- md5: c3ff5f718d335a37374717ad9197b16f
mtime: 1342684709
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7499
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: dbb8f6bc3df07371d63248770be979d4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: prusnak
number: 128439
source_package: zsh
source_project: shells
source_rev: '103'
state: accepted
type: submit
rev: 41.0
unexpanded_srcmd5: b84c0e53e8110d924040a7b8c84b431f
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- we need tex2html too, which is provided by texinfo (forwarded request
128654 from coolo)'
commit_time: 2012-07-23 10:49:16
expanded_srcmd5: 694ea6fe3443d74f087976739689f870
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: 64add6b356176ec8ff8df4f74433a607
mtime: 1342963271
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21757
- md5: 7988318584889ff0a74799db34b8814b
mtime: 1342963271
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7523
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 81244eb50c48321c4af80684ba684c1a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: elvigia
number: 128701
source_package: zsh
source_project: shells
source_rev: '105'
state: accepted
type: submit
rev: 42.0
unexpanded_srcmd5: 694ea6fe3443d74f087976739689f870
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Version update to 5.0.0\n * No real changes since 4.3.17"
commit_time: 2012-08-12 15:30:03
expanded_srcmd5: e772cdb34a36b02c9a132052c5f9b856
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: e8484468925cec8d9a84b8b04797e764
mtime: 1344547718
name: zsh-5.0.0.tar.bz2
size: 3014362
- md5: c35eda4b363fa64eadd3af3c0b7a717d
mtime: 1344547719
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21934
- md5: 02f5139fb20ac1950959bc399f083b5f
mtime: 1344547719
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7557
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 6e6ac8e856c2ae731d2230ef761138a4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 130572
source_package: zsh
source_project: shells
source_rev: '107'
state: accepted
type: submit
rev: 43.0
unexpanded_srcmd5: e772cdb34a36b02c9a132052c5f9b856
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- buildrequire groff needed to build helpfiles (forwarded request 139458
from coolo)'
commit_time: 2012-10-27 07:58:13
expanded_srcmd5: 8bc5614105e55a60ea62e2d46eae4659
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: e8484468925cec8d9a84b8b04797e764
mtime: 1344547718
name: zsh-5.0.0.tar.bz2
size: 3014362
- md5: a724f2ec3d6b1e582c113a4e58fadc6c
mtime: 1351263550
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22097
- md5: adfe942b8c83b4f09db5a2ae89db7bab
mtime: 1351263550
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7579
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 031af487ec2aecb3d9d49928e440efb3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: elvigia
number: 139476
source_package: zsh
source_project: shells
source_rev: '109'
state: accepted
type: submit
rev: 44.0
unexpanded_srcmd5: 8bc5614105e55a60ea62e2d46eae4659
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Test suite runs flaky in qemu-arm, disable it for now. (forwarded request
141528 from elvigia)'
commit_time: 2012-11-16 14:53:30
expanded_srcmd5: 590c03cab81b061cb15c43fb5f4f1d3d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: e8484468925cec8d9a84b8b04797e764
mtime: 1344547718
name: zsh-5.0.0.tar.bz2
size: 3014362
- md5: b0e0712f6bec2e725fcf4772d1076827
mtime: 1353037796
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22281
- md5: 0d12279d9148a3282deafe7d485ffe20
mtime: 1353037796
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7618
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: d68dbde25cd77bb2bdcc2b0f1192cbfc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 141535
source_package: zsh
source_project: shells
source_rev: '111'
state: accepted
type: submit
rev: 45.0
unexpanded_srcmd5: 590c03cab81b061cb15c43fb5f4f1d3d
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.0.2\n * Numeric constants in mathematical contexts\
\ can contain\n underscores.\n * functions -T turns on tracing for specific\
\ functions.\n- See the included NEWS file for other changes."
commit_time: 2012-12-28 22:52:35
expanded_srcmd5: 3be6f553505c2671079ec7d0ed8d2324
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: c590c6fe96a83e3c19826a21c573a628
mtime: 1356365274
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22607
- md5: 160658f1a239bb03c0ff2a3711935eea
mtime: 1356365274
name: zsh.spec
size: 7618
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 99784ec72be9d34fe3b9b5c8fc06adef
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 146351
source_package: zsh
source_project: shells
source_rev: '113'
state: accepted
type: submit
rev: 46.0
unexpanded_srcmd5: 3be6f553505c2671079ec7d0ed8d2324
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Split 12.3 from Factory
commit_time: 2013-01-25 11:46:27
expanded_srcmd5: 3be6f553505c2671079ec7d0ed8d2324
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: c590c6fe96a83e3c19826a21c573a628
mtime: 1356365274
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22607
- md5: 160658f1a239bb03c0ff2a3711935eea
mtime: 1356365274
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7618
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 99784ec72be9d34fe3b9b5c8fc06adef
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 47.0
unexpanded_srcmd5: 3be6f553505c2671079ec7d0ed8d2324
userid: adrianSuSE
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Fix zypper completion [bnc#752112]\n * zsh-zypper-completion.patch\n\
- Fix osc completion\n * zsh-osc-suseversion.patch (forwarded request 150103\
\ from Dmitry_R)"
commit_time: 2013-01-29 06:49:17
expanded_srcmd5: 38f80ccc1c3b02286389eb5d01babf69
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 4a720655df5f9a4e06bb0b58d638e90d
mtime: 1359320185
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22866
- md5: c0262cdcaf8febecb926b2c541fc6bad
mtime: 1359320186
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7728
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 9b71c978b8160351ba287df4f4442ab3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 150181
source_package: zsh
source_project: shells
source_rev: '115'
state: accepted
type: submit
rev: 48.0
unexpanded_srcmd5: 38f80ccc1c3b02286389eb5d01babf69
userid: coolo
- broken: false
comment: "- Fix custom completion support via /etc/zsh_completion.d\n- Add trim-unneeded-completions.patch\
\ to remove unneeded completions\n when building for openSUSE"
commit_time: 2013-03-22 09:22:17
expanded_srcmd5: 04180169faf63064a20734cc5dbb861a
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 2091b0e3067a5f26d58b984498bd89ae
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23140
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b24c178ed619c49c96c3f5a5d892d778
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7013
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: c16224131ae6b5af341c8f3e76650219
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 160415
source_package: zsh
source_project: shells
source_rev: '117'
state: accepted
type: submit
rev: 49.0
unexpanded_srcmd5: 04180169faf63064a20734cc5dbb861a
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Automatic submission by obs-autosubmit
commit_time: 2013-04-02 14:02:24
expanded_srcmd5: 74cb28a802517e1bad1c316055ac8f54
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 13191c1949a36561e5ff7bded0aefbc5
mtime: 1364212982
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23153
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b24c178ed619c49c96c3f5a5d892d778
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7013
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 0c85534f82c7d97056a5e9b9fae5561f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: factory-maintainer
number: 162040
source_package: zsh
source_project: shells
source_rev: '119'
state: accepted
type: submit
rev: 50.0
unexpanded_srcmd5: 74cb28a802517e1bad1c316055ac8f54
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Don''t set globdots it might lead to unexpected problems (bnc#815556)'
commit_time: 2013-04-22 14:33:18
expanded_srcmd5: 3e6b7d3422aa654974b14c1717fe45ec
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 90989bcb959ec1eedf45f0644b578dc1
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23343
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 3a35f5322f5d10a8a9baadcd26a00ede
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 172801
source_package: zsh
source_project: shells
source_rev: '121'
state: accepted
type: submit
rev: 51.0
unexpanded_srcmd5: 3e6b7d3422aa654974b14c1717fe45ec
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Split 13.1 from Factory
commit_time: 2013-09-20 10:19:56
expanded_srcmd5: 3e6b7d3422aa654974b14c1717fe45ec
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 90989bcb959ec1eedf45f0644b578dc1
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23343
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 3a35f5322f5d10a8a9baadcd26a00ede
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 52.0
unexpanded_srcmd5: 3e6b7d3422aa654974b14c1717fe45ec
userid: adrianSuSE
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.0.4\n * Small bugfix release\n- Add zsh-pipefix.patch\
\ to import pipe fixes from zsh.git\n- Remove upstream patches\n * zsh-osc-suseversion.patch\n\
\ * zsh-zypper-completion.patch"
commit_time: 2013-12-26 17:42:43
expanded_srcmd5: 1593e4d587cbc15f2ccffef809243d70
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 9829fe8932c25740173a272e8959cf8c
mtime: 1387974935
name: zsh-5.0.4.tar.bz2
size: 3093541
- md5: 3df7a2ee980fef6584c80866b354c64b
mtime: 1387974936
name: zsh-pipefix.patch
size: 4982
- md5: 8187ab74fb60a442f2aad6ad4aaeeebf
mtime: 1387974936
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23658
- md5: b17085bdef79aa398d95d2827d24331e
mtime: 1387974937
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7617
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 6e9d70daeb1bbe8ca55faf042af89fab
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 212246
source_package: zsh
source_project: shells
source_rev: '123'
state: accepted
type: submit
rev: 53.0
unexpanded_srcmd5: 1593e4d587cbc15f2ccffef809243d70
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.0.5\n * Fixes a couple of regression in 5.0.4\n\
- Remove zsh-pipefix.patch, merged upstream"
commit_time: 2014-01-07 13:59:54
expanded_srcmd5: 15d875d25397b389ec36b8250c3014a3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: db249ac47a319c9f1d787ce9399c100c
mtime: 1389084347
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23888
- md5: 396d67b584bd94b235d56a2e2eb8a9cb
mtime: 1389084347
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: aaabe91b75c883ae7a9c7c5b425f1be9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 212971
source_package: zsh
source_project: shells
source_rev: '125'
state: accepted
type: submit
rev: 54.0
unexpanded_srcmd5: 15d875d25397b389ec36b8250c3014a3
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Add zsh-update-zypper-completion.patch to update zypper\n completions,\
\ patch by Holger Macht and Thomas Mitterfellner."
commit_time: 2014-01-16 15:38:30
expanded_srcmd5: 836efa37e7d9eafe3416d841ae766810
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: c1f3030f64aabc337391359b08a9fbe1
mtime: 1389865918
name: zsh-update-zypper-completion.patch
size: 4955
- md5: 7cb93087378c06bcc0f8fded1109f369
mtime: 1389865918
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24127
- md5: ccc468f3cd96471e5023892f034392ca
mtime: 1389865919
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7634
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 53a76d1b7a632ccca87afc9a4feb7da1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 214085
source_package: zsh
source_project: shells
source_rev: '127'
state: accepted
type: submit
rev: 55.0
unexpanded_srcmd5: 836efa37e7d9eafe3416d841ae766810
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Update zsh-update-zypper-completion.patch to v0.3'
commit_time: 2014-01-17 13:18:37
expanded_srcmd5: 491824607345a8ce61ea213ea2a668c5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: 1698a635df56fc7b1479f583bfbc78f9
mtime: 1389951758
name: zsh-update-zypper-completion.patch
size: 7349
- md5: 30fdad3feaabf19c58228f3930e584c0
mtime: 1389951758
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24297
- md5: ccc468f3cd96471e5023892f034392ca
mtime: 1389865919
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7634
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 58970e8c8ee1504a2f1bdc254649b505
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 214151
source_package: zsh
source_project: shells
source_rev: '129'
state: accepted
type: submit
rev: 56.0
unexpanded_srcmd5: 491824607345a8ce61ea213ea2a668c5
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Rename Completion/openSUSE/Command/_SuSEconfig to _SUSEconfig\n (bnc#888989\
\ fate#316521)"
commit_time: 2014-08-07 08:07:33
expanded_srcmd5: 3bbe746d24b0310191a563e58edad140
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: 1698a635df56fc7b1479f583bfbc78f9
mtime: 1389951758
name: zsh-update-zypper-completion.patch
size: 7349
- md5: c9c3a4bb3c8fa775e437a7e3a0e530d0
mtime: 1407330156
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24506
- md5: d8c1957c2f5f22b4c3755fcec2edc8c0
mtime: 1407330157
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7805
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c55596398820f508757a1fff16ac4395
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 243775
source_package: zsh
source_project: shells
source_rev: '131'
state: accepted
type: submit
rev: 57.0
unexpanded_srcmd5: 3bbe746d24b0310191a563e58edad140
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Split 13.2 from Factory
commit_time: 2014-08-29 11:18:02
expanded_srcmd5: 3bbe746d24b0310191a563e58edad140
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: 1698a635df56fc7b1479f583bfbc78f9
mtime: 1389951758
name: zsh-update-zypper-completion.patch
size: 7349
- md5: c9c3a4bb3c8fa775e437a7e3a0e530d0
mtime: 1407330156
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24506
- md5: d8c1957c2f5f22b4c3755fcec2edc8c0
mtime: 1407330157
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7805
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c55596398820f508757a1fff16ac4395
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
rev: 58.0
unexpanded_srcmd5: 3bbe746d24b0310191a563e58edad140
userid: adrianSuSE
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.0.6\n * See included ChangeLog\n- Remove zsh-update-zypper-completion.patch,\
\ fixed upstream"
commit_time: 2014-08-31 09:58:42
expanded_srcmd5: 4da6ed237313605918f57b1e8f08f1c8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7150a6abc2aa1a79d81ed9a282594225
mtime: 1409253794
name: zsh-5.0.6.tar.bz2
size: 3174858
- md5: 11bea0ecc6068fb59c1f3c57bf571fed
mtime: 1409253799
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24737
- md5: 3632b6e3e20f84225b59b880043cd37b
mtime: 1409253804
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 8945ed679c7b8f6f4c1ca68425a1a361
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 246763
source_package: zsh
source_project: shells
source_rev: '133'
state: accepted
type: submit
rev: 59.0
unexpanded_srcmd5: 4da6ed237313605918f57b1e8f08f1c8
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Add zsh-fix-pcre-n.patch to fix pcre_match() -n option'
commit_time: 2014-09-10 07:27:36
expanded_srcmd5: 54157fdda195c7863e44b27e4e5130da
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7150a6abc2aa1a79d81ed9a282594225
mtime: 1409253794
name: zsh-5.0.6.tar.bz2
size: 3174858
- md5: d71962d3be318f52490cb5e51bd1704a
mtime: 1410120662
name: zsh-fix-pcre-n.patch
size: 1323
- md5: 9665f91c4d58971709cc61903f3829ed
mtime: 1410120662
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24913
- md5: 9660338847959ec0914b5fd07741bf1c
mtime: 1410120662
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7669
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: b7e7f41de9c6c27cd754ee483db15485
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 247923
source_package: zsh
source_project: shells
source_rev: '135'
state: accepted
type: submit
rev: 60.0
unexpanded_srcmd5: 54157fdda195c7863e44b27e4e5130da
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.0.7\n * Small bugfixes\n * Includes a security\
\ fix to disallow evaluation of the\n initial values of integer variables imported\
\ from the environment\n- Remove zsh-fix-pcre-n.patch, fixed upstream"
commit_time: 2014-10-11 19:24:56
expanded_srcmd5: 86d3a790490434346e5d27462e3f4f38
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: ac1800b0d2ed2a73bd930bef1aa4a734
mtime: 1412843248
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25250
- md5: fd28c254e838e5330edd69f0dc0a1c90
mtime: 1412843249
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 083238867e93473aa3db8264083cf984
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 254813
source_package: zsh
source_project: shells
source_rev: '138'
state: accepted
type: submit
rev: 61.0
unexpanded_srcmd5: 86d3a790490434346e5d27462e3f4f38
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Harden CFLAGS/LDFLAGS'
commit_time: 2015-01-20 19:11:51
expanded_srcmd5: 87a3f9fe487aa61b9a4dbd18ef2860e6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: 2315777b505818b9384dd63cb98a2eec
mtime: 1421229733
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25393
- md5: 995140977eae1f567e6642e19dfa1882
mtime: 1421229733
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7620
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 502ccf75f66255f5035d000449cd6056
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 281259
source_package: zsh
source_project: shells
source_rev: '140'
state: accepted
type: submit
rev: 62.0
unexpanded_srcmd5: 87a3f9fe487aa61b9a4dbd18ef2860e6
userid: dimstar_suse
- broken: false
comment: '- Add back rpm completion file (bnc#900424)'
commit_time: 2015-01-30 20:30:57
expanded_srcmd5: ee0a7e034a7c10ada458ec6c4e304bf9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: fa48f01c66839d1106d53a63fe63f17a
mtime: 1422467630
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25556
- md5: 285faaf320d1b1a0473491b97450e0ad
mtime: 1422467631
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7727
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: db7093ae63e5815fc7e3145229be54a1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 283223
source_package: zsh
source_project: shells
source_rev: '142'
state: accepted
type: submit
rev: 63.0
unexpanded_srcmd5: ee0a7e034a7c10ada458ec6c4e304bf9
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '1'
commit_time: 2015-02-16 15:02:26
expanded_srcmd5: 841a989452fb68c2846b0ef0c9831480
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: 394a47bfaf59878df6aeb96fc532d6a9
mtime: 1423556907
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25770
- md5: 321a2a622a197a4857cf0e4d2f7cf446
mtime: 1423556907
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7729
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 2fd40e4b8f5ab6888736c0ed2e7bfab8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 285134
source_package: zsh
source_project: shells
source_rev: '146'
state: accepted
type: submit
rev: 64.0
unexpanded_srcmd5: 841a989452fb68c2846b0ef0c9831480
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '1'
commit_time: 2015-04-25 16:46:10
expanded_srcmd5: a22d19dcf0b6ba9beeb3105b47214000
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: 0ebe981224e759c6bba935e8663afb9b
mtime: 1429699576
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25956
- md5: 321a2a622a197a4857cf0e4d2f7cf446
mtime: 1423556907
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7729
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 7bb8f67e6f0c63eb5d7f17dd82a03218
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 298564
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '148'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 65.0
unexpanded_srcmd5: a22d19dcf0b6ba9beeb3105b47214000
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '1'
commit_time: 2015-05-10 10:53:51
expanded_srcmd5: 04a1f0f9fdcc5be3e6f2b177aabe17fd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fce6580dd4278ca92446d7ffcb627f38
mtime: 1430296444
name: gcc5-fix.patch
size: 468
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: f3d3899d680e44767c56e35e88a71287
mtime: 1430638602
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 26329
- md5: 9324bf96b7525a93dbdb6dd4f6848d54
mtime: 1430638602
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7914
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: a6657188268650bda75e1085939de5aa
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 305205
source_package: zsh
source_project: shells
source_rev: '151'
state: accepted
type: submit
rev: 66.0
unexpanded_srcmd5: 04a1f0f9fdcc5be3e6f2b177aabe17fd
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.0.8\n * Global aliases can be created for syntactic\
\ tokens such as command\n separators (\";\", \"&\", \"|\", \"&&\", \"||\"\
), redirection operators, etc.\n * There have been various further improvements\
\ to builtin handling\n with the POSIX_BUILTINS option (off by default) for\
\ compatibility with\n the POSIX standard.\n * 'whence -v' is now more informative,\
\ and 'whence -S' shows you\n how a full chain of symbolic links resolves to\
\ a command.\n * The 'p' parameter flag now allows an argument to be specified\n\
\ as a reference to a variable, e.g. ${(ps.$sep.)foo} to split $foo\n on\
\ a string given by $sep.\n * The option FORCE_FLOAT now forces variables, not\
\ just constants,\n to floating point in arithmetic expressions.\n * The type\
\ of an assignment in arithmetic expressions, e.g. the\n type seen by the variable\
\ res in $(( res = a = b )), is now\n more logical and C-like.\n * The default\
\ binding of 'u' in vi command mode has changed to undo\n multiple changes\
\ when invoked repeatedly. '^R' is now bound to redo\n changes. To revert to\
\ toggling of the last edit use:\n bindkey -a u vi-undo-change\n * Compatibility\
\ with Vim has been improved for vi editing mode. Most\n notably, Vim style\
\ text objects are supported and the region can be\n manipulated with vi commands\
\ in the same manner as Vim's visual mode.\n * Elements of the watch variable\
\ may now be patterns.\n * The logic for retrying history locking has been improved.\n\
- Remove gcc5-fix.patch, fixed upstream."
commit_time: 2015-06-03 08:23:27
expanded_srcmd5: cd4f502a63775f7828fbe633ec1129ab
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e6759e8dd7b714d624feffd0a73ba0fe
mtime: 1433100363
name: zsh-5.0.8.tar.bz2
size: 3250542
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: c83f49e1cc811e275cb96f5f5cb4ec88
mtime: 1433146212
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 27964
- md5: cc2685c7c066a633ba41ee58cf5ff90f
mtime: 1433100364
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7837
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 5b76c251cd4dedd67e6aaeab9ec16921
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 309607
source_package: zsh
source_project: shells
source_rev: '154'
state: accepted
type: submit
rev: 67.0
unexpanded_srcmd5: cd4f502a63775f7828fbe633ec1129ab
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Automatic submission by obs-autosubmit
commit_time: 2015-07-05 17:57:05
expanded_srcmd5: 57bab987029be9c9b3a67ccda4234d17
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 50e8e43fa9519084aed3fbd0ce48486e
mtime: 1434286715
name: printf-regress.patch
size: 1465
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e6759e8dd7b714d624feffd0a73ba0fe
mtime: 1433100363
name: zsh-5.0.8.tar.bz2
size: 3250542
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 783892cf2e97d048f5c56f60127ace6a
mtime: 1434286715
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 28148
- md5: 974d43106fe62b4637df3a6c7f2e3f8b
mtime: 1434286715
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7886
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 5e7f6dc2b19eea85a043428f0accc288
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: factory-maintainer
number: 312924
source_package: zsh
source_project: shells
source_rev: '156'
state: accepted
type: submit
rev: 68.0
unexpanded_srcmd5: 57bab987029be9c9b3a67ccda4234d17
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Add read1char_signals.patch to fix workers/36373 \n\n- Update to version\
\ 5.1\n * The print builtin has new options -x and -X to expand tabs.\n * Several\
\ new command completions and numerous updates to others.\n * Options to \"fc\"\
\ to segregate internal and shared history.\n * All emulations including \"sh\"\
\ use multibyte by default; several\n repairs to multibyte handling.\n * ZLE\
\ supports \"bracketed paste\" mode to avoid interpreting pasted\n newlines\
\ as accept-line. Pastes can be highlighted for visibility\n and to make it\
\ more obvious whether accept-line has occurred.\n * Improved (though still not\
\ perfect) POSIX compatibility for getopts\n builtin when POSIX_BUILTINS is\
\ set.\n * New setopt APPEND_CREATE for POSIX-compatible NO_CLOBBER behavior.\n\
\ * Completion of date values now displays in a calendar format when\n the\
\ complist module is available. Controllable by zstyle.\n * New parameter UNDO_LIMIT_NO\
\ for more control over ZLE undo repeat.\n * Several repairs/improvements to\
\ the contributed narrow-to-region\n ZLE function.\n * Many changes to child-process\
\ and signal handling to eliminate race\n conditions and avoid deadlocks on\
\ descriptor and memory management.\n * New builtin sysopen in zsh/system module\
\ for detailed control of\n file descriptor modes. \n- Remove printf-regress.patch,\
\ upstream."
commit_time: 2015-09-03 17:59:47
expanded_srcmd5: 69e8a0a0b735985221308da290199b51
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7635c7a8fa92c8b4a5b2dfceaea18c4a
mtime: 1441134043
name: read1char_signals.patch
size: 807
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fbf736a6540873f4fb7bdaf70cafb1f0
mtime: 1441089950
name: zsh-5.1.tar.xz
size: 2785404
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: aa388d4e667870dce0a8ccfe331bf73f
mtime: 1441134044
name: zsh.changes
size: 29718
- md5: e87cd182b100cd1986675dea811f2482
mtime: 1441134044
name: zsh.spec
size: 7886
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 73978081312a4c555d49ec66a716f31b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 328399
source_package: zsh
source_project: shells
source_rev: '160'
state: accepted
type: submit
rev: 69.0
unexpanded_srcmd5: 69e8a0a0b735985221308da290199b51
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.1.1\n * Bug fixes for regressions in 5.1 release\n\
- Remove read1char_signals.patch, fixed upstream."
commit_time: 2015-09-17 09:18:28
expanded_srcmd5: 8c0a1fe3db6d257e581b93dd09818b7b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0e8ea3313300277a04cee80836507bae
mtime: 1442044314
name: zsh-5.1.1.tar.xz
size: 2788676
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: b373c644fdb74d070e09016ba23ff0bf
mtime: 1442044314
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 29957
- md5: 8aa1991aa4061b24681f1f9db48769cd
mtime: 1442044314
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7836
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: fe0bc941e6a894a0522de986c48d31b7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 330592
source_package: zsh
source_project: shells
source_rev: '162'
state: accepted
type: submit
rev: 70.0
unexpanded_srcmd5: 8c0a1fe3db6d257e581b93dd09818b7b
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Remove -Wl,-z,now it breaks module loading rh#1277996'
commit_time: 2015-11-08 14:35:23
expanded_srcmd5: a30570e033ee5847880c61ff538315a4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0e8ea3313300277a04cee80836507bae
mtime: 1442044314
name: zsh-5.1.1.tar.xz
size: 2788676
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: bf2ecdb63a1d8b7aa8300916e05e6cea
mtime: 1446738981
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 30132
- md5: 4ec0662ba4b45c2883d457e4a6501571
mtime: 1446738982
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7830
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: bd3d3b4790c024d6e9df6f1c605035cf
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 342578
source_package: zsh
source_project: shells
source_rev: '164'
state: accepted
type: submit
rev: 71.0
unexpanded_srcmd5: a30570e033ee5847880c61ff538315a4
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.2\n * The new module zsh/param/private can be loaded\
\ to allow the shell\n to define parameters that are private to a function\
\ scope (i.e. are\n not propagated to nested functions called within this function).\n\
\ * The GLOB_STAR_SHORT option allows the pattern **/* to be shortened to\n \
\ just ** if no / follows. so **.c searches recursively for a file whose\n \
\ name has the suffix \".c\".\n * The effect of the WARN_CREATE_GLOBAL option\
\ has been significantly\n extended, so expect it to cause additional warning\
\ messages about\n parameters created globally within function scope."
commit_time: 2015-12-09 19:32:40
expanded_srcmd5: 778e06fe1df8d2e9beefe52ec2b7e5c9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 514ca876eeda0637438f6a625acc9f7b
mtime: 1449132574
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 30860
- md5: 0ac4793bf97921d9251b7ecb95bbe6e6
mtime: 1449132574
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7828
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: cb9a89c02eebb560cbaf94bc8a6237cc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 347277
source_package: zsh
source_project: shells
source_rev: '166'
state: accepted
type: submit
rev: 72.0
unexpanded_srcmd5: 778e06fe1df8d2e9beefe52ec2b7e5c9
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '1'
commit_time: 2015-12-17 15:53:50
expanded_srcmd5: 244c8e81ab6074e2468284fa7424a768
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 630efb1373c1c13886e634a3e43eb408
mtime: 1449741347
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 30999
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
- md5: 544cdb737350efa356e01c9b5c83cd35
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7925
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: b825c459249c9249366621fc1e12c26d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 348221
source_package: zsh
source_project: shells
source_rev: '168'
state: accepted
type: submit
rev: 73.0
unexpanded_srcmd5: 244c8e81ab6074e2468284fa7424a768
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Automatic submission by obs-autosubmit
commit_time: 2016-06-05 14:19:58
expanded_srcmd5: bc24cad5875c68f9d221c01b304b8ed5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 0858cb2acc70799dbeb6cfd749fae8f6
mtime: 1464179454
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 31139
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
- md5: ae01b84db82eafd09f94896a78e3e750
mtime: 1464141876
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8282
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: c689695a5eb0e7f87e21912ee21790cb
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: factory-maintainer
number: 399482
source_package: zsh
source_project: shells
source_rev: '171'
state: accepted
type: submit
rev: 74.0
unexpanded_srcmd5: bc24cad5875c68f9d221c01b304b8ed5
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '1'
commit_time: 2016-09-05 21:13:52
expanded_srcmd5: c39ddbf837f3a3a1fdb8bfa9dce2f24b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bd92b62261b623aab9a7818a9e447577
mtime: 1467385699
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 109
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: b6dfdc650f23b39d4f925fe492e7f422
mtime: 1472566992
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 31429
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
- md5: 9d36aa82b521f7cc8eb3f0f02e464bf3
mtime: 1467386605
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8005
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 4bd7916fbf341f02fa9fc2e0ac3f06b9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 423967
source_package: zsh
source_project: shells
source_rev: '173'
state: accepted
type: submit
rev: 75.0
unexpanded_srcmd5: c39ddbf837f3a3a1fdb8bfa9dce2f24b
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Read /etc/profile as zsh again.'
commit_time: 2016-09-08 18:05:51
expanded_srcmd5: 4f763cf22894367659b053a1b0733656
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ae98396f495b7b6aefc7dac0b894753e
mtime: 1473341143
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 93
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 0e413add5169d47bd51331792d0e3b89
mtime: 1473341143
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 31582
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
- md5: 9d36aa82b521f7cc8eb3f0f02e464bf3
mtime: 1467386605
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8005
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 9a2d3412a736d0bbd2c0d7a0b4b8b518
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 425719
source_package: zsh
source_project: shells
source_rev: '175'
state: accepted
type: submit
rev: 76.0
unexpanded_srcmd5: 4f763cf22894367659b053a1b0733656
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to zsh 5.3\n * Unicode9 support, this needs support from your\
\ terminal to\n work correctly.\n * The new word modifier ':P' computes the\
\ physical path of the\n argument.\n * The output of \"typeset -p\" uses \"\
export\" commands or the \"-g\"\n option for parameters that are not local\
\ to the current scope.\n * vi-repeat-change can repeat user-defined widgets\
\ if the widget\n calls zle -f vichange.\n * The parameter $registers now\
\ makes the contents of vi register\n buffers available to user-defined widgets.\n\
\ * New vi-up-case and vi-down-case builtin widgets bound to gU/gu\n (or U/u\
\ in visual mode) for doing case conversion.\n * A new select-word-match function\
\ provides vim-style text objects\n with configurable word boundaries using\
\ the existing\n match-words-by-style mechanism.\n * Support for the conditional\
\ expression [[ -v var ]] to test if a\n variable is set for compatibility\
\ with other shells.\n * The print and printf builtins have a new option -v to\
\ assign the\n output to a variable.\n * New x: syntax in completion match\
\ specifications make it possible\n to disable match specifications hardcoded\
\ in completion functions.\n- Re-add custom zshrc and zshenv to unbreak compatibility\
\ with old\n usage (boo#998858).\n- Add fix-printf.patch to fix a regression\
\ in printf."
commit_time: 2016-12-16 11:59:34
expanded_srcmd5: 7afccf46ae6135fc959c3079d38d4544
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 70d75ef84294c274243d2b35b184ae60
mtime: 1481709716
name: fix-printf.patch
size: 842
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: c5ba34e68fcf62a2e78adc56bf3d328a
mtime: 1481709717
name: zsh-5.3.tar.xz
size: 2928684
- md5: 9b38eec96ec1a6b579b3486087f39a33
mtime: 1481709717
name: zsh-5.3.tar.xz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 029877695a09eeffe8398e7cec633c09
mtime: 1481710011
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 33012
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
- md5: 09d6e402123636148e4a39fdd9d46c67
mtime: 1481709717
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8221
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 3af848ae1f0ef13dc66ced7fdbee1b9e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 445732
source_package: zsh
source_project: shells
source_rev: '178'
state: accepted
type: submit
rev: 77.0
unexpanded_srcmd5: 7afccf46ae6135fc959c3079d38d4544
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '1'
commit_time: 2017-02-11 01:30:57
expanded_srcmd5: bafa4532823bb7b22150bc212721e58a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8ce1dd8955386daf1606d3c33283e1b
mtime: 1484066059
name: fix-patchutils-completion.patch
size: 1269
- md5: 70d75ef84294c274243d2b35b184ae60
mtime: 1481709716
name: fix-printf.patch
size: 842
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: c5ba34e68fcf62a2e78adc56bf3d328a
mtime: 1481709717
name: zsh-5.3.tar.xz
size: 2928684
- md5: 9b38eec96ec1a6b579b3486087f39a33
mtime: 1481709717
name: zsh-5.3.tar.xz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 440839cf8b232d05669ab7ae20c604cf
mtime: 1484066060
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 33219
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
- md5: 62bfb6a9a38bda5db737ebae0b952a6e
mtime: 1484066060
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8281
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 427ac21acbe4fc61ed51fa69586cf3ea
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 455002
source_package: zsh
source_project: shells
source_rev: '180'
state: accepted
type: submit
rev: 78.0
unexpanded_srcmd5: bafa4532823bb7b22150bc212721e58a
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '1'
commit_time: 2017-03-10 20:44:29
expanded_srcmd5: bd82cfb489adb0ac815367b6e7792f39
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8ce1dd8955386daf1606d3c33283e1b
mtime: 1484066059
name: fix-patchutils-completion.patch
size: 1269
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: 67d3e5ed99de68340c16aef613b0ecf7
mtime: 1488724478
name: zsh-5.3.1.tar.xz
size: 2928832
- md5: a0b1584fddb060b6696482f5f5e8b2c8
mtime: 1488724478
name: zsh-5.3.1.tar.xz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: fbf2c668a30d9d92b4663d594adc8006
mtime: 1488725930
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 33571
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
- md5: ef95dd047dd456b17b96f56ac8d8d1ae
mtime: 1488724895
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8201
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 585cb13a8765112b9e6e4a29bc97ebf2
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 477054
source_package: zsh
source_project: shells
source_rev: '182'
state: accepted
type: submit
rev: 79.0
unexpanded_srcmd5: bd82cfb489adb0ac815367b6e7792f39
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2018-03-01 12:02:03
expanded_srcmd5: 028eb07119574a2828c5b38ef854c97c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: dfe156fd69b0d8d1745ecf6d6e02e047
mtime: 1519734333
name: zsh-5.4.2.tar.gz
size: 4482413
- md5: 10b4764a0350d83198142ce09cc99b63
mtime: 1519734333
name: zsh-5.4.2.tar.gz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 42e088293cb7dd58b871e8ea373965f1
mtime: 1519734333
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 34332
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
- md5: f72350f79eca0a08a490fd920a7829f9
mtime: 1519734333
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8141
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 1981ade0ca8bcf73a50e57d12301a8e8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 580596
source_package: zsh
source_project: shells
source_rev: '184'
state: accepted
type: submit
rev: 80.0
unexpanded_srcmd5: 028eb07119574a2828c5b38ef854c97c
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2018-04-26 13:32:32
expanded_srcmd5: e0bea4d270d352e09c22fc9d4cdc96ce
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: 2430c85bd128c59f5c0806ef00d3ea8d
mtime: 1523433151
name: zsh-5.5.tar.gz
size: 4576506
- md5: e328d710dab08b85df0c5b3cc314f7c7
mtime: 1523433151
name: zsh-5.5.tar.gz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 6d9d12882367c941f04e65cfc1e96fb7
mtime: 1523533099
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 35408
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
- md5: cb032e2a26137c38cfd941cac3777562
mtime: 1523533099
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8049
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: c75a1a1830effcab26c6c640004c9f13
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 595955
source_package: zsh
source_project: shells
source_rev: '187'
state: accepted
type: submit
rev: 81.0
unexpanded_srcmd5: e0bea4d270d352e09c22fc9d4cdc96ce
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2018-05-16 11:24:02
expanded_srcmd5: d1a2d12179de67fa707b2f7d22d41490
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: 678bc037a7311a46e7fc0adca7ed8266
mtime: 1526046115
name: zsh-5.5.1.tar.gz
size: 4578700
- md5: f9c86b6d33b701c8af3bf1be87f0b0da
mtime: 1526046115
name: zsh-5.5.1.tar.gz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 18d0b3484a7b35bf793fdf9f706bdd2f
mtime: 1526046115
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 35661
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
- md5: 624d83b1b8d8d7bd1847ada9e0255a7e
mtime: 1526046115
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8051
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 05315558e7ee9013f616212e8d0fd467
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 606966
source_package: zsh
source_project: shells
source_rev: '189'
state: accepted
type: submit
rev: 82.0
unexpanded_srcmd5: d1a2d12179de67fa707b2f7d22d41490
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.6\n * Fixes CVE-2018-0502 (bsc#1107296) and\n \
\ CVE-2018-13259 (bsc#1107294)\n * Switch to -fstack-protector-strong\n *\
\ See included NEWS file for complete changes.\n- No longer manually install help\
\ files, make install handles it.\n- Workaround a regression upstream with help\
\ file generation by\n removing Doc/help.txt before build.\n\n * fix for a configuration\
\ problem finding signal names from (some) recent"
commit_time: 2018-09-07 15:35:17
expanded_srcmd5: 85d2d22a9a50606f78de2d9cc7e161b3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: 4890f422e6f3c5127a19c8f6b867f292
mtime: 1536077556
name: zsh-5.6.tar.xz
size: 3080856
- md5: 1aa29cd686e88b8c92120c69f0c60ab4
mtime: 1536133170
name: zsh-5.6.tar.xz.asc
size: 1276
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 519968ed0a8ed6cb46b991516d081641
mtime: 1536158251
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36151
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
name: zsh.keyring
size: 9441
- md5: 43a5742b4a7dfbebaad8521df6c75c04
mtime: 1536137959
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7979
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: c97047f0bf3e1e013a2eb5137f8280e0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 633489
source_package: zsh
source_project: shells
source_rev: '195'
state: accepted
type: submit
rev: 83.0
unexpanded_srcmd5: 85d2d22a9a50606f78de2d9cc7e161b3
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2018-09-18 11:39:51
expanded_srcmd5: 428ea691ccf0aa5031ba5b0d04b5bdf0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: 540673bf823d2e13806ac0395caa8345
mtime: 1537128881
name: zsh-5.6.2.tar.xz
size: 3077368
- md5: a3b09dbf98e917b33dcac74604fbfe10
mtime: 1537128881
name: zsh-5.6.2.tar.xz.asc
size: 821
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: a979a9d5bd8840ef45074c7b9ab9773d
mtime: 1537128881
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36691
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
name: zsh.keyring
size: 9441
- md5: 887122b0be8ff982bcd97e08c85fc6e0
mtime: 1537128881
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7889
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 4bdc85b2d710e4f713cda1fadc4957ce
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 636300
source_package: zsh
source_project: shells
source_rev: '199'
state: accepted
type: submit
rev: 84.0
unexpanded_srcmd5: 428ea691ccf0aa5031ba5b0d04b5bdf0
userid: maxlin_factory
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Unbreak Leap 42.3 compilation \n\n- Update to version 5.6.2"
commit_time: 2018-10-01 09:04:03
expanded_srcmd5: 6255916c9153892a7b24161a10925680
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: 540673bf823d2e13806ac0395caa8345
mtime: 1537128881
name: zsh-5.6.2.tar.xz
size: 3077368
- md5: a3b09dbf98e917b33dcac74604fbfe10
mtime: 1537128881
name: zsh-5.6.2.tar.xz.asc
size: 821
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 2ceec3757bf465ee58a653e762399824
mtime: 1537522189
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36858
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
name: zsh.keyring
size: 9441
- md5: 0715e41b2b3671c4842183ff65677326
mtime: 1537522189
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8020
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: d5f1be96b97956d30c0050615b7494a3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 637013
source_package: zsh
source_project: shells
source_rev: '202'
state: accepted
type: submit
rev: 85.0
unexpanded_srcmd5: 6255916c9153892a7b24161a10925680
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.7.1\n * This release contains fixes for the two\
\ regressions reported\n with VCS_Info and prompt colour sequences.\n\n- Update\
\ to version 5.7\n * Support for 24-bit true color terminals has been added.\n\
\ Hex triplets can be used when specifying colours for prompts\n and line\
\ editor highlighting. On 88 and 256 colour terminals,\n a new zsh/nearcolor\
\ module allows colours specified with hex\n triplets to be matched against\
\ the nearest available colour.\n * The zsh/datetime module's strftime builtin\
\ now accepts an\n argument specifying the nanoseconds time component; both\n\
\ arguments can be omitted to use the current time."
commit_time: 2019-02-04 21:10:56
expanded_srcmd5: fde226c6d6db981f59796f6f30b1912c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: 374f9fdd121b5b90e07abfcad7df0627
mtime: 1549286549
name: zsh-5.7.1.tar.xz
size: 3126308
- md5: 877554b2be677f34e8c8657a884f3e05
mtime: 1549286549
name: zsh-5.7.1.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: b6f19dc4caf1ec2dc6899ce7ce733ea3
mtime: 1549286549
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 37788
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: d58e44ee47cc7540040cb7ffde36a868
mtime: 1549286549
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8096
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: a19366bda32fe0f0cf6428975b695c85
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 671123
source_package: zsh
source_project: shells
source_rev: '205'
state: accepted
type: submit
rev: 86.0
unexpanded_srcmd5: fde226c6d6db981f59796f6f30b1912c
userid: coolo
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.8~pre2 (5.7.1-test-2)\n- Drop 1baf0d1f553631ecb641e98f4bf48bc2a44e5b82.patch,\
\ fixed\n upstream.\n\n- Add 1baf0d1f553631ecb641e98f4bf48bc2a44e5b82.patch to\
\ fix a\n re-entrancy problem.\n\n- Update to version 5.8~pre1 (5.7.1-test-1)\n\
\ * The zsh/zutil module's zparseopts builtin learnt an -F option to abort\n\
\ parsing when an unrecognised option-like parameter is encountered.\n * The\
\ zsh/files module gained a chmod builtin.\n * Several changes have been made\
\ to the way completion functions track\n 'precommands' (such as `command`\
\ and `env`) and determine whether the\n command being completed for is a shell\
\ builtin. Developers of completion\n functions may wish to familiarise themselves\
\ with `_normal -p` and\n `_pick_variant -b`.\n * The option CD_SILENT was\
\ added to suppress all output from cd (whether\n explicit or implicit with\
\ AUTO_CD). It is disabled by default.\n * The compadd builtin's -o option now\
\ takes an optional argument to\n specify the order of completion matches.\
\ This affects the display\n of candidate matches and the order in which they\
\ are selected when\n cycling between them using menu completion.\n * The\
\ :h and :t modifiers in parameter expansion (if braces are present),\n glob\
\ qualifiers and history expansion may take following decimal digit\n arguments\
\ in order to keep that many leading or trailing path components\n instead\
\ of the defaults of all but one (:h) and one (:t). In an absolute\n path\
\ the leading '/' counts as one component.\n * The functions builtin gained a\
\ -c option to efficiently copy functions.\n- See included ChangeLog for the complete\
\ list of changes."
commit_time: 2019-12-23 22:42:01
expanded_srcmd5: e01b2e451be0c4a6cd2c32bdbd08e46a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: b82302ee34c9fd53afc247160f2e581a
mtime: 1577006875
name: zsh-5.7.1-test-2.tar.xz
size: 3180532
- md5: 00cffae3c868465f9e2aca90de129876
mtime: 1577006876
name: zsh-5.7.1-test-2.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 67f6cb55fb132d4f408abdab29914852
mtime: 1577006876
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 39845
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: e2f1e3aeed148a7b58b7d3c77dfd1a64
mtime: 1577006877
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8163
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 29840d573e65443efa0b3fd060bfc547
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 758830
source_package: zsh
source_project: shells
source_rev: '210'
state: accepted
type: submit
rev: 87.0
unexpanded_srcmd5: e01b2e451be0c4a6cd2c32bdbd08e46a
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.8~pre3 (5.7.1-test-3)\n * Minor bugfixes compared\
\ to pre2"
commit_time: 2020-02-15 22:23:25
expanded_srcmd5: e05d121e79129cdf6d8424ecaf970493
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: d757e713284cfed2c68865b32b6a5743
mtime: 1581077516
name: zsh-5.7.1-test-3.tar.xz
size: 3188996
- md5: 8d7eb6a4c07d3e5ff08575355118760a
mtime: 1581077516
name: zsh-5.7.1-test-3.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 677c52627be5f5624a75238ffc064c09
mtime: 1581077516
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40060
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 385a160ec728eabbe36f605389b4ef4d
mtime: 1581077516
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8163
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 2f9c8c0f0023626dddd5b9c8a732793c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 771563
source_package: zsh
source_project: shells
source_rev: '212'
state: accepted
type: submit
rev: 88.0
unexpanded_srcmd5: e05d121e79129cdf6d8424ecaf970493
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.8\n * Fixes CVE-2019-20044 bsc#1163882"
commit_time: 2020-02-20 14:53:48
expanded_srcmd5: 60e9627c8c5ac250189fee593883b0aa
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 43a4fba3bbfa4b4b12f78c3969ad019a
mtime: 1581941552
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40256
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 1d6aa472172299aadc6720ce0c2f2c45
mtime: 1581917359
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8066
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 4b163e04d058ed7f25d8150888a4eca6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 774851
source_package: zsh
source_project: shells
source_rev: '215'
state: accepted
type: submit
rev: 89.0
unexpanded_srcmd5: 60e9627c8c5ac250189fee593883b0aa
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2020-03-11 18:45:53
expanded_srcmd5: d48e23bf442bc279d2cdc9243a1921c8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: b78fc56158d6a9644682055f0c65fe65
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40457
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7911
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: c7e5cab3cf46d4964ccf50ab627c7d86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 783235
source_package: zsh
source_project: shells
source_rev: '217'
state: accepted
type: submit
rev: 90.0
unexpanded_srcmd5: d48e23bf442bc279d2cdc9243a1921c8
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Stop sourcing /etc/bash.bashrc which causes problems with ls, add\n\
\ a call to manually source /etc/zsh.zshrc.local if available."
commit_time: 2020-04-13 12:51:40
expanded_srcmd5: 6c17a999a0fe28cde35d17547712a34d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 3e5514ec3a821f22db41452c7e3f307c
mtime: 1586326131
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40723
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7911
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 45b24dd95a40884324f3b362516ade14
mtime: 1586326131
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7305
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: d9971d5f3928360c68210898e3b0dd0b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 792416
source_package: zsh
source_project: shells
source_rev: '219'
state: accepted
type: submit
rev: 91.0
unexpanded_srcmd5: 6c17a999a0fe28cde35d17547712a34d
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Add aliases from /etc/bash.bashrc into /etc/zshrc so we don't\n regress"
commit_time: 2020-04-16 22:58:55
expanded_srcmd5: f2501827a6884ca5f8be44b163aeb18d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: a7e8a7b1e8a6acb4634b7d803a4c1555
mtime: 1586941565
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40932
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7911
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ffbd0d215490f7ebc2fdade4eacfa426
mtime: 1586941565
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7874
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: ab172d8c93c010602ccd2704d088f933
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 794119
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: shells
source_rev: '221'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 92.0
unexpanded_srcmd5: f2501827a6884ca5f8be44b163aeb18d
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2020-05-08 23:00:58
expanded_srcmd5: 78098ab430e048079a00fed58a88abab
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 111604bf070fafdd380d98715e98fc35
mtime: 1588709286
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 41323
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7911
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 939c99c187ae38e220e9ad634eb3dfae
mtime: 1588709223
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8907
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 05fa5eb65d182b8841e05be47754484b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 800536
source_package: zsh
source_project: shells
source_rev: '225'
state: accepted
type: submit
rev: 93.0
unexpanded_srcmd5: 78098ab430e048079a00fed58a88abab
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2020-10-06 17:06:09
expanded_srcmd5: 8b60d8465a4b00d5a903377c3d4ea2d9
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a8e2acb46201b1f5a2543734b764a1c6
mtime: 1598597687
name: ncurses-fix.patch
size: 2509
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: f0d7436956b2f8627856df81c9d4fed7
mtime: 1598361971
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 41512
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: fbda7ba8a6efa07d4f3ddfa62fd25593
mtime: 1598361971
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7957
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 2f67bda66a72670ab82e7e81102e4bc5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 830225
source_package: zsh
source_project: shells
source_rev: '228'
state: accepted
type: submit
rev: 94.0
unexpanded_srcmd5: 8b60d8465a4b00d5a903377c3d4ea2d9
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2020-12-02 13:57:45
expanded_srcmd5: 39185a1ed232a87da4547ec2c3e62891
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a8e2acb46201b1f5a2543734b764a1c6
mtime: 1598597687
name: ncurses-fix.patch
size: 2509
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fea885aee6a9923e3e7873dd45c94927
mtime: 1604415550
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 41678
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: cc4dd727f21675db36df4e2ea3ac81b3
mtime: 1605885302
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8062
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 5cc2dd4280b976d4c11e04a7fe105aae
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: namtrac
number: 851932
source_package: zsh
source_project: shells
source_rev: '230'
state: accepted
type: submit
rev: 95.0
unexpanded_srcmd5: 39185a1ed232a87da4547ec2c3e62891
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2022-03-28 17:00:11
expanded_srcmd5: 29e1a6c9f2bce4d9cf40b02ae8528708
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a8e2acb46201b1f5a2543734b764a1c6
mtime: 1598597687
name: ncurses-fix.patch
size: 2509
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 063a98c256ee0584b3c115924e41a332
mtime: 1644825326
name: zsh-5.8.1.tar.xz
size: 3200540
- md5: 8f0910bb736c51fff575d02a389e49bb
mtime: 1644825326
name: zsh-5.8.1.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ea40a2a4fcfb6a3ed0c7aa299c312b08
mtime: 1647806704
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 42817
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6535db04b5697b61452ad3bf03b29232
mtime: 1644825327
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8064
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 108d3cba85c441301b8d6338eb7ace5b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: pperego
number: 964828
source_package: zsh
source_project: shells
source_rev: 20d1708ef4ee9a2ee7188d03f41903a7
state: accepted
type: submit
rev: 96.0
unexpanded_srcmd5: 29e1a6c9f2bce4d9cf40b02ae8528708
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2022-05-25 20:34:07
expanded_srcmd5: ad4003544c1e5883cc7845aec88cacb4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: 182e37ca3fe3fa6a44f69ad462c5c30e
mtime: 1652636844
name: zsh-5.9.tar.xz
size: 3332400
- md5: a19a373a7650a9a629323a4364e1bc79
mtime: 1652636844
name: zsh-5.9.tar.xz.asc
size: 488
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d670cd2425647286b81a126f4c85809
mtime: 1652636844
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 48221
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 3ab19f0f7098edc637f5e25500d03276
mtime: 1652636844
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8059
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: ae89175d8b4c0ecde5db52a3a1d5f5a3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: openSUSE:Factory
request:
creator: pperego
number: 979023
source_package: zsh
source_project: shells
source_rev: b9d92abdfe63b8bf7c71388342e69981
state: accepted
type: submit
rev: 97.0
unexpanded_srcmd5: ad4003544c1e5883cc7845aec88cacb4
userid: dimstar_suse
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2022-09-14 13:44:33
expanded_srcmd5: 116386845907990b642d3d1887c8025a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 3896df2dd48cc8d813ed5ae050ebdbbc
mtime: 1662987947
name: egrep-deprecation.patch
size: 883
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: 182e37ca3fe3fa6a44f69ad462c5c30e
mtime: 1652636844
name: zsh-5.9.tar.xz
size: 3332400
- md5: a19a373a7650a9a629323a4364e1bc79
mtime: 1652636844
name: zsh-5.9.tar.xz.asc
size: 488
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bf8d364cf9f23065f6bbba63930bdbc6
mtime: 1662987948
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 48400
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 692aed08bb8ddab9a86883b0d5d31e8c
mtime: 1662989807
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8195
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 1372ffe69a925e1acc78948fc13279f8
package: zsh
project: openSUSE:Factory
request:
creator: pperego
number: 1003249
source_package: zsh
source_project: shells
source_rev: 4097e03edf23505d3129bdfa412e0399
state: accepted
type: submit
rev: 98.0
unexpanded_srcmd5: 116386845907990b642d3d1887c8025a
userid: dimstar_suse
- broken: false
comment: ''
commit_time: 2006-10-23 14:15:27
expanded_srcmd5: e32a05e1287a91442b5c835b966a2f80
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
files_hash: f89e311f97454be9b1c03d08e49be30e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 1.0
unexpanded_srcmd5: e32a05e1287a91442b5c835b966a2f80
userid: unknown
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2006-10-23 14:15:31
expanded_srcmd5: 47c9ddb1d622be4524585af6a3a79b4d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
files_hash: f5f255c0a229b746c8a0ea8b5defbb3a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 2.0
unexpanded_srcmd5: 47c9ddb1d622be4524585af6a3a79b4d
userid: unknown
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2006-10-23 14:15:38
expanded_srcmd5: 4d8ef63d2169261cd66b9c48aebdc1ce
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
files_hash: 700de7e1513d1cdaccf30897454088fc
package: zsh
project: shells
rev: 3.0
unexpanded_srcmd5: 4d8ef63d2169261cd66b9c48aebdc1ce
userid: unknown
- broken: false
comment: ''
commit_time: 2006-10-23 14:15:48
expanded_srcmd5: 0418c639e2abe324fbb40fef2752e975
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
files_hash: 6bee28d02b3b78c7c4783249ce179c59
package: zsh
project: shells
rev: 4.0
unexpanded_srcmd5: 0418c639e2abe324fbb40fef2752e975
userid: unknown
- broken: false
comment: ''
commit_time: 2006-10-23 14:15:51
expanded_srcmd5: b1bb41dcff60e79be9b0bb1f174eb550
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
files_hash: 1dcabe058f6bea9a042c1f461c9e6410
package: zsh
project: shells
rev: 5.0
unexpanded_srcmd5: b1bb41dcff60e79be9b0bb1f174eb550
userid: unknown
- broken: false
comment: ''
commit_time: 2006-10-23 14:15:54
expanded_srcmd5: 4098dde5435674b70803c8527bf8d6a1
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
files_hash: 78653b8e5fa3d4774970bc9ea4a16c07
package: zsh
project: shells
rev: 6.0
unexpanded_srcmd5: 4098dde5435674b70803c8527bf8d6a1
userid: unknown
- broken: false
comment: ''
commit_time: 2006-10-23 14:15:58
expanded_srcmd5: a3affcee7cc723653f78181fb0c6ba2b
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
files_hash: 60a6d8ddc7a38f25f2996700a5c8f86e
package: zsh
project: shells
rev: 7.0
unexpanded_srcmd5: a3affcee7cc723653f78181fb0c6ba2b
userid: unknown
- broken: false
comment: ''
commit_time: 2006-10-23 14:16:09
expanded_srcmd5: d0014c5be0d2a0d102f6a058db5da4d2
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
files_hash: 78b8f45efdf3531960a9a53f15bb1fe0
package: zsh
project: shells
rev: 8.0
unexpanded_srcmd5: d0014c5be0d2a0d102f6a058db5da4d2
userid: unknown
- broken: false
comment: ''
commit_time: 2006-10-23 14:16:19
expanded_srcmd5: 2ffc56477e6b8dd127b38c47f7b3b454
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
files_hash: 747ca2547a64b6861335f8b545d1ca49
package: zsh
project: shells
rev: 9.0
unexpanded_srcmd5: 2ffc56477e6b8dd127b38c47f7b3b454
userid: unknown
- broken: false
comment: ''
commit_time: 2006-10-23 14:16:20
expanded_srcmd5: 3c7d74534c14b073d105759c6e0c3704
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
- md5: e73e3324c45852959171975f8a77ee97
mtime: 1161591945
name: zsh.changes
size: 10842
files_hash: 16ec4eeea1c0b74e8020dd6f9d94985d
package: zsh
project: shells
rev: 10.0
unexpanded_srcmd5: 3c7d74534c14b073d105759c6e0c3704
userid: unknown
- broken: false
comment: ''
commit_time: 2006-10-23 14:16:22
expanded_srcmd5: 75ebe90eab0abfbdd8b5d3e68ec3788e
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
- md5: e73e3324c45852959171975f8a77ee97
mtime: 1161591945
name: zsh.changes
size: 10842
- md5: 52ab752f4e84df9fa5bf86611b36e242
mtime: 1161591946
name: zsh.spec
size: 9713
files_hash: 5e6f8490a2e1529bf875a9d7be60e93c
package: zsh
project: shells
rev: 11.0
unexpanded_srcmd5: 75ebe90eab0abfbdd8b5d3e68ec3788e
userid: unknown
- broken: false
comment: ''
commit_time: 2006-10-23 14:16:24
expanded_srcmd5: 27fb7e9f01a3b23994778accbf76063d
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
- md5: e73e3324c45852959171975f8a77ee97
mtime: 1161591945
name: zsh.changes
size: 10842
- md5: 52ab752f4e84df9fa5bf86611b36e242
mtime: 1161591946
name: zsh.spec
size: 9713
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
files_hash: 2e13fc9a749fe95f94dbaebf1dc2c9dc
package: zsh
project: shells
rev: 12.0
unexpanded_srcmd5: 27fb7e9f01a3b23994778accbf76063d
userid: unknown
- broken: false
comment: ''
commit_time: 2006-10-23 14:16:26
expanded_srcmd5: 7790ada8f5f035c8e941809b48682c56
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
- md5: e73e3324c45852959171975f8a77ee97
mtime: 1161591945
name: zsh.changes
size: 10842
- md5: 52ab752f4e84df9fa5bf86611b36e242
mtime: 1161591946
name: zsh.spec
size: 9713
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 1c65b8438b9313624487ff6a385ae64e
mtime: 1142381840
name: zshrc
size: 6825
files_hash: 1b9b0347bb6834b45c6ba83be70eacb3
package: zsh
project: shells
rev: 13.0
unexpanded_srcmd5: 7790ada8f5f035c8e941809b48682c56
userid: unknown
- broken: false
comment: ''
commit_time: 2007-04-19 19:47:15
expanded_srcmd5: 6b252a9c7647df71c7634239459af151
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: e73e3324c45852959171975f8a77ee97
mtime: 1161591945
name: zsh.changes
size: 10842
- md5: 52ab752f4e84df9fa5bf86611b36e242
mtime: 1161591946
name: zsh.spec
size: 9713
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 1c65b8438b9313624487ff6a385ae64e
mtime: 1142381840
name: zshrc
size: 6825
files_hash: fd9d6462616685b305b6ad49ea498ea8
package: zsh
project: shells
rev: 14.0
unexpanded_srcmd5: 6b252a9c7647df71c7634239459af151
userid: unknown
- broken: false
comment: ''
commit_time: 2007-04-19 19:47:18
expanded_srcmd5: ef5a02e3a49216af83755fb56dbb3854
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: e73e3324c45852959171975f8a77ee97
mtime: 1161591945
name: zsh.changes
size: 10842
- md5: 52ab752f4e84df9fa5bf86611b36e242
mtime: 1161591946
name: zsh.spec
size: 9713
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 1c65b8438b9313624487ff6a385ae64e
mtime: 1142381840
name: zshrc
size: 6825
files_hash: c44e21eda2936e042e0dc054ceb21090
package: zsh
project: shells
rev: 15.0
unexpanded_srcmd5: ef5a02e3a49216af83755fb56dbb3854
userid: unknown
- broken: false
comment: ''
commit_time: 2007-04-19 19:47:20
expanded_srcmd5: e68163dd436ccc8c7cdd63f529549087
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: e73e3324c45852959171975f8a77ee97
mtime: 1161591945
name: zsh.changes
size: 10842
- md5: 52ab752f4e84df9fa5bf86611b36e242
mtime: 1161591946
name: zsh.spec
size: 9713
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 1c65b8438b9313624487ff6a385ae64e
mtime: 1142381840
name: zshrc
size: 6825
files_hash: 7bc3f19049d21c7f3f0dd523a8059060
package: zsh
project: shells
rev: 16.0
unexpanded_srcmd5: e68163dd436ccc8c7cdd63f529549087
userid: unknown
- broken: false
comment: ''
commit_time: 2007-04-19 19:47:20
expanded_srcmd5: 12b0f3505de5d0b6dd2384dd3229c892
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: ca4480682273ef59aff37288532684ee
mtime: 1177004840
name: zsh.changes
size: 11196
- md5: 52ab752f4e84df9fa5bf86611b36e242
mtime: 1161591946
name: zsh.spec
size: 9713
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 1c65b8438b9313624487ff6a385ae64e
mtime: 1142381840
name: zshrc
size: 6825
files_hash: 37d566141527cab8b15f75fe380d2142
package: zsh
project: shells
rev: 17.0
unexpanded_srcmd5: 12b0f3505de5d0b6dd2384dd3229c892
userid: unknown
- broken: false
comment: ''
commit_time: 2007-04-19 19:47:21
expanded_srcmd5: aee9dae22aa9d9d982b37747982ffd6b
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 45ec02997b222a2bda99fae80f4cda86
mtime: 1144866533
name: zsh-4.3.1.diff
size: 21965
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: ca4480682273ef59aff37288532684ee
mtime: 1177004840
name: zsh.changes
size: 11196
- md5: e0b6c2f285532c7b92feda9336f31060
mtime: 1177004841
name: zsh.spec
size: 4263
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 1c65b8438b9313624487ff6a385ae64e
mtime: 1142381840
name: zshrc
size: 6825
files_hash: 13f91c7e5f8a72d021cc75f647989590
package: zsh
project: shells
rev: 18.0
unexpanded_srcmd5: aee9dae22aa9d9d982b37747982ffd6b
userid: unknown
- broken: false
comment: ''
commit_time: 2007-04-19 19:47:22
expanded_srcmd5: 7cae67c58d3e790a65822a9e5534217c
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 69d1ab9d179d7d16eb0251a0a60e0457
mtime: 1144406832
name: zsh-4.3.2-doc.tar.bz2
size: 2207375
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: ca4480682273ef59aff37288532684ee
mtime: 1177004840
name: zsh.changes
size: 11196
- md5: e0b6c2f285532c7b92feda9336f31060
mtime: 1177004841
name: zsh.spec
size: 4263
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 1c65b8438b9313624487ff6a385ae64e
mtime: 1142381840
name: zshrc
size: 6825
files_hash: af0db3b57ef77e260515b5ca99a4aa99
package: zsh
project: shells
rev: 19.0
unexpanded_srcmd5: 7cae67c58d3e790a65822a9e5534217c
userid: unknown
- broken: false
comment: ''
commit_time: 2007-04-19 19:47:23
expanded_srcmd5: ac47f5aa035ea87bebd4882397a6d36e
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: e13fc4bb338fbb27ef7508a474310c8f
mtime: 1144406816
name: zsh-4.3.2.tar.bz2
size: 2263544
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: ca4480682273ef59aff37288532684ee
mtime: 1177004840
name: zsh.changes
size: 11196
- md5: e0b6c2f285532c7b92feda9336f31060
mtime: 1177004841
name: zsh.spec
size: 4263
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 1c65b8438b9313624487ff6a385ae64e
mtime: 1142381840
name: zshrc
size: 6825
files_hash: 472d055dfaa6a8c25bed183ee5d897fb
package: zsh
project: shells
rev: 20.0
unexpanded_srcmd5: ac47f5aa035ea87bebd4882397a6d36e
userid: unknown
- broken: false
comment: ''
commit_time: 2007-04-19 19:47:24
expanded_srcmd5: 99afa4cffbfdf51399fc1c556f27eb64
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: ca4480682273ef59aff37288532684ee
mtime: 1177004840
name: zsh.changes
size: 11196
- md5: e0b6c2f285532c7b92feda9336f31060
mtime: 1177004841
name: zsh.spec
size: 4263
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 1c65b8438b9313624487ff6a385ae64e
mtime: 1142381840
name: zshrc
size: 6825
files_hash: 11a7a70ca032e0a295ec684925fcc039
package: zsh
project: shells
rev: 21.0
unexpanded_srcmd5: 99afa4cffbfdf51399fc1c556f27eb64
userid: unknown
- broken: false
comment: ''
commit_time: 2007-07-04 17:04:43
expanded_srcmd5: e9a08148a3ca4813069a12414025c34c
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: 839c1f8e922615691ad7824e504f118f
mtime: 1183561483
name: zsh.changes
size: 11297
- md5: e0b6c2f285532c7b92feda9336f31060
mtime: 1177004841
name: zsh.spec
size: 4263
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 1c65b8438b9313624487ff6a385ae64e
mtime: 1142381840
name: zshrc
size: 6825
files_hash: e42337d95e871dddd5dbdefb77c734c4
package: zsh
project: shells
rev: 22.0
unexpanded_srcmd5: e9a08148a3ca4813069a12414025c34c
userid: unknown
- broken: false
comment: ''
commit_time: 2007-07-04 17:04:44
expanded_srcmd5: 615965f474ca6ff183dca0224a5bc177
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: 839c1f8e922615691ad7824e504f118f
mtime: 1183561483
name: zsh.changes
size: 11297
- md5: 4c812ddffd91ccbc65515d5f6131348f
mtime: 1183561484
name: zsh.spec
size: 4266
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 1c65b8438b9313624487ff6a385ae64e
mtime: 1142381840
name: zshrc
size: 6825
files_hash: 798065375020dc0a76235f80ac769ddd
package: zsh
project: shells
rev: 23.0
unexpanded_srcmd5: 615965f474ca6ff183dca0224a5bc177
userid: unknown
- broken: false
comment: ''
commit_time: 2007-07-04 17:04:45
expanded_srcmd5: 515973bc6ae97c95046627fa78952434
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: 839c1f8e922615691ad7824e504f118f
mtime: 1183561483
name: zsh.changes
size: 11297
- md5: 4c812ddffd91ccbc65515d5f6131348f
mtime: 1183561484
name: zsh.spec
size: 4266
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: b653d60e25094de2a45b8ef74d589736
mtime: 1183561484
name: zshrc
size: 6814
files_hash: a966103f11f22495b22cf326742e71d6
package: zsh
project: shells
rev: 24.0
unexpanded_srcmd5: 515973bc6ae97c95046627fa78952434
userid: unknown
- broken: false
comment: ''
commit_time: 2009-08-05 13:19:22
expanded_srcmd5: 92bca5f88b48499b986cf7cbce80d2e2
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: cab29228a90f58b1431a66ab24a0a0c2
mtime: 1207266567
name: zsh-4.3.6-doc.tar.bz2
size: 2473544
- md5: 16f399af1081ad3c303a794c9c7dc47e
mtime: 1207266568
name: zsh-4.3.6.tar.bz2
size: 2527972
- md5: 839c1f8e922615691ad7824e504f118f
mtime: 1183561483
name: zsh.changes
size: 11297
- md5: 4c812ddffd91ccbc65515d5f6131348f
mtime: 1183561484
name: zsh.spec
size: 4266
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: b653d60e25094de2a45b8ef74d589736
mtime: 1183561484
name: zshrc
size: 6814
files_hash: f64dfeaa824ec9797279d6be15558f04
package: zsh
project: shells
rev: 25.0
unexpanded_srcmd5: 7dd16e861a05e7ff9340c19f72522f97
userid: hennevogel
- broken: false
comment: ''
commit_time: 2009-08-05 14:10:19
expanded_srcmd5: c55703b8825ebb47bfb0c2f8307a0123
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: cab29228a90f58b1431a66ab24a0a0c2
mtime: 1207266567
name: zsh-4.3.6-doc.tar.bz2
size: 2473544
- md5: 16f399af1081ad3c303a794c9c7dc47e
mtime: 1207266568
name: zsh-4.3.6.tar.bz2
size: 2527972
- md5: 839c1f8e922615691ad7824e504f118f
mtime: 1183561483
name: zsh.changes
size: 11297
- md5: 4c812ddffd91ccbc65515d5f6131348f
mtime: 1183561484
name: zsh.spec
size: 4266
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: b653d60e25094de2a45b8ef74d589736
mtime: 1183561484
name: zshrc
size: 6814
files_hash: f64dfeaa824ec9797279d6be15558f04
package: zsh
project: shells
rev: 26.0
unexpanded_srcmd5: b9db1652d2fc9e702ffe5298988528e0
userid: hennevogel
- broken: false
comment: ''
commit_time: 2009-08-05 14:15:10
expanded_srcmd5: 3f604d60b7b409b868114402c09719bb
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 1a4ab09a9d75c5ae8585ad645406f27d
mtime: 1177004835
name: zsh-4.3.4-doc.tar.bz2
size: 2358063
- md5: 33b41656f94e867df6e15a17081c58dc
mtime: 1177004840
name: zsh-4.3.4.diff
size: 22989
- md5: 8410a30e4f5c6160790bc3afc096424f
mtime: 1177004838
name: zsh-4.3.4.tar.bz2
size: 2374851
- md5: cab29228a90f58b1431a66ab24a0a0c2
mtime: 1207266567
name: zsh-4.3.6-doc.tar.bz2
size: 2473544
- md5: 16f399af1081ad3c303a794c9c7dc47e
mtime: 1207266568
name: zsh-4.3.6.tar.bz2
size: 2527972
- md5: 839c1f8e922615691ad7824e504f118f
mtime: 1183561483
name: zsh.changes
size: 11297
- md5: 4c812ddffd91ccbc65515d5f6131348f
mtime: 1183561484
name: zsh.spec
size: 4266
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: b653d60e25094de2a45b8ef74d589736
mtime: 1183561484
name: zshrc
size: 6814
files_hash: f64dfeaa824ec9797279d6be15558f04
package: zsh
project: shells
rev: 27.0
unexpanded_srcmd5: 9707e0d620620dfdd6b3dd52d2fb5f7e
userid: hennevogel
- broken: false
comment: update to 4.3.10.
commit_time: 2009-08-12 21:02:43
expanded_srcmd5: 35fbd113774bef8272a0e97fbb7c0ae5
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: 8b82adb733fee208ca3bee089b516795
mtime: 1250103762
name: zsh.changes
size: 12864
- md5: c2936bc978f7575d3a95fdcd5093b8ae
mtime: 1250103763
name: zsh.spec
size: 4597
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: b653d60e25094de2a45b8ef74d589736
mtime: 1183561484
name: zshrc
size: 6814
files_hash: 3824e023addf6028a67c979afde67431
package: zsh
project: shells
rev: 28.0
unexpanded_srcmd5: 73a7c2713c3fa8ecff1a95b0bff4d49f
userid: hennevogel
- broken: false
comment: merge changes files
commit_time: 2009-08-18 12:50:46
expanded_srcmd5: c5dc16a0562b1718faf126f9d393fa27
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c8e1db4ea4393ffdec4a36eb052fa354
mtime: 1250592645
name: zsh.changes
size: 15596
- md5: c2936bc978f7575d3a95fdcd5093b8ae
mtime: 1250103763
name: zsh.spec
size: 4597
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: b653d60e25094de2a45b8ef74d589736
mtime: 1183561484
name: zshrc
size: 6814
files_hash: 5aa7d5b588edf4e204d72cdbf4f28bae
package: zsh
project: shells
rev: 29.0
unexpanded_srcmd5: 68065b64fbb1c03a89864640bdf42a2e
userid: hennevogel
- broken: false
comment: merge back OBS changes
commit_time: 2009-08-18 12:54:37
expanded_srcmd5: 5feb44b38b2674431c35f85eb2dc6c5e
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c8e1db4ea4393ffdec4a36eb052fa354
mtime: 1250592645
name: zsh.changes
size: 15596
- md5: d5b1aab8db5f5bac296e55aa27dc46da
mtime: 1250592877
name: zsh.spec
size: 4721
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: b653d60e25094de2a45b8ef74d589736
mtime: 1183561484
name: zshrc
size: 6814
files_hash: 522a4f029f9e5e5bbaf3234b23d1b865
package: zsh
project: shells
rev: 30.0
unexpanded_srcmd5: c618da3c290bd66c3ec5b47a96c2bd2f
userid: hennevogel
- broken: false
comment: checked in
commit_time: 2009-08-19 00:11:23
expanded_srcmd5: 3c3aa49f78394a78e3695346af19353b
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 954b7757c741a5ff7460f6d3de3503f2
mtime: 1144878410
name: zsh-4.2.5-tailsyntax.diff
size: 432
- md5: 05c98cf9ac6ab622e0dd10706ebca6b5
mtime: 1144866534
name: zsh-4.3.1-91.diff
size: 371
- md5: 0370558bcd27b6aeea54a0dc6a215b57
mtime: 1206073029
name: zsh-4.3.4.diff
size: 9298
- md5: cab29228a90f58b1431a66ab24a0a0c2
mtime: 1207266567
name: zsh-4.3.6-doc.tar.bz2
size: 2473544
- md5: 16f399af1081ad3c303a794c9c7dc47e
mtime: 1207266568
name: zsh-4.3.6.tar.bz2
size: 2527972
- md5: 7131dcf1e0848eadb6466da7558e0d6a
mtime: 1240575342
name: zsh.changes
size: 14029
- md5: d8836d243949cf13dd574d8b4b273747
mtime: 1243265339
name: zsh.spec
size: 12709
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 1b5f336a1ae38528a7dd3bad24f9a117
package: zsh
project: shells
rev: 31.0
unexpanded_srcmd5: 363d287c5ccf7d7e264be799eabfa45a
userid: autobuild
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 12.0
commit_time: 2009-08-19 00:11:24
expanded_srcmd5: 50384adce2f3e6af59dd61ac09892f99
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c8e1db4ea4393ffdec4a36eb052fa354
mtime: 1250592645
name: zsh.changes
size: 15596
- md5: a431a22b103004ec80d92abc8f3080bb
mtime: 1250633484
name: zsh.spec
size: 5181
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: b653d60e25094de2a45b8ef74d589736
mtime: 1183561484
name: zshrc
size: 6814
files_hash: cbc154833f9bdb7d2d9b04fe1b63ecb3
package: zsh
project: shells
rev: 31.012
unexpanded_srcmd5: 363d287c5ccf7d7e264be799eabfa45a
userid: buildservice-autocommit
- broken: false
comment: fix zshrc
commit_time: 2009-08-20 12:52:45
expanded_srcmd5: 293e599d9af6e2da4ad47d1f77ee16a2
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: b84ef89cabc22933fcd33a677cd2cb8f
mtime: 1250765564
name: zsh.changes
size: 15776
- md5: a431a22b103004ec80d92abc8f3080bb
mtime: 1250633484
name: zsh.spec
size: 5181
- md5: 846883a31dd4e1769ab0e808a7e22317
mtime: 1142381839
name: zshenv
size: 157
- md5: 6ffbe150389e89af407e1a2aed1f9639
mtime: 1250765564
name: zshrc
size: 6918
files_hash: 2f8b6ba6a2ea775f52c66566df6c0c66
package: zsh
project: shells
rev: 32.0
unexpanded_srcmd5: eb3ae1918c00d5882652db2f0a63fde0
userid: hennevogel
- broken: false
comment: fix zshrc and zshenv
commit_time: 2009-08-20 13:18:10
expanded_srcmd5: 43ad55ead8176c87c0083644b6bb2b8b
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: b84ef89cabc22933fcd33a677cd2cb8f
mtime: 1250765564
name: zsh.changes
size: 15776
- md5: a431a22b103004ec80d92abc8f3080bb
mtime: 1250633484
name: zsh.spec
size: 5181
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 7bc2678821300a0358063c5db97de486
package: zsh
project: shells
rev: 33.0
unexpanded_srcmd5: 40264a551d27fcfef176ed8cc8d994c2
userid: hennevogel
- broken: true
comment: Updating link to change in openSUSE:Factory/zsh revision 13.0
commit_time: 2009-08-21 18:41:30
expanded_srcmd5: null
files: []
files_hash: null
package: zsh
project: shells
rev: 33.013
unexpanded_srcmd5: 40264a551d27fcfef176ed8cc8d994c2
userid: buildservice-autocommit
- broken: false
comment: checked in
commit_time: 2009-08-21 18:41:30
expanded_srcmd5: 9974014a79db2db6b48ee1c39aa30f89
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: b84ef89cabc22933fcd33a677cd2cb8f
mtime: 1250765564
name: zsh.changes
size: 15776
- md5: 11040c40cb2b37049b33d4e395cb3c06
mtime: 1250872890
name: zsh.spec
size: 5181
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: c1e181638f1088544b5fa395704558ec
package: zsh
project: shells
rev: 34.0
unexpanded_srcmd5: 18b75c1b1309d1973406ba2713c6cde8
userid: autobuild
- broken: false
comment: '
- disable profiling for now'
commit_time: 2009-10-08 18:23:29
expanded_srcmd5: 9e381f584d8783b8e54fc24c619e6d3e
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: a0f91c040db93d6a49e8d85ded5e4dfd
mtime: 1255019009
name: zsh.changes
size: 15922
- md5: ab43c8c5b5e81a69ad1116e25537fd9a
mtime: 1255019009
name: zsh.spec
size: 5205
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: ddba2e795f2c6205c9e315f31b32b4c0
package: zsh
project: shells
rev: 35.0
unexpanded_srcmd5: cc02d4fb852a0568affb304b240eacb9
userid: coolo
- broken: false
comment: checked in
commit_time: 2009-10-13 17:27:28
expanded_srcmd5: 4a5cf1980db553fa0fa0a9599b8cd0e1
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: b84ef89cabc22933fcd33a677cd2cb8f
mtime: 1250765564
name: zsh.changes
size: 15776
- md5: 11040c40cb2b37049b33d4e395cb3c06
mtime: 1250872890
name: zsh.spec
size: 5181
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: c1e181638f1088544b5fa395704558ec
package: zsh
project: shells
rev: 36.0
unexpanded_srcmd5: e38996d6ee694258a69fc97495196bb6
userid: autobuild
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 14.0
commit_time: 2009-10-13 17:27:29
expanded_srcmd5: 2a30eb0ee9c15cde957832981547ee00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: a0f91c040db93d6a49e8d85ded5e4dfd
mtime: 1255019009
name: zsh.changes
size: 15922
- md5: 26336ee303cb6d45a1ca215383c7fd05
mtime: 1255447649
name: zsh.spec
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 18d5fc82295b89ec951ed46159c0b3cd
package: zsh
project: shells
rev: 36.014
unexpanded_srcmd5: e38996d6ee694258a69fc97495196bb6
userid: buildservice-autocommit
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 15.0
commit_time: 2009-10-13 17:27:29
expanded_srcmd5: 2a30eb0ee9c15cde957832981547ee00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: a0f91c040db93d6a49e8d85ded5e4dfd
mtime: 1255019009
name: zsh.changes
size: 15922
- md5: 26336ee303cb6d45a1ca215383c7fd05
mtime: 1255447649
name: zsh.spec
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 18d5fc82295b89ec951ed46159c0b3cd
package: zsh
project: shells
rev: 36.029
unexpanded_srcmd5: e38996d6ee694258a69fc97495196bb6
userid: buildservice-autocommit
- broken: false
comment: 'Copy from home:coolo:branches:openSUSE:Factory/zsh via accept of submit
request 25424 revision 2.
Request was accepted with message:
'
commit_time: 2009-12-03 17:38:48
expanded_srcmd5: a331c9dbe6504564b7140b1faa6ea6f5
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: 1d2c10dfbf731be6a2702062c0a2a568
mtime: 1259777956
name: zsh.changes
size: 16076
- md5: 26336ee303cb6d45a1ca215383c7fd05
mtime: 1255447649
name: zsh.spec
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: fd60619d7cf701decd3876efaa6fbe77
package: zsh
project: shells
request:
creator: coolo
number: 25424
source_package: zsh
source_project: home:coolo:branches:openSUSE:Factory
source_rev: '2'
state: accepted
type: submit
rev: 37.0
unexpanded_srcmd5: 72b3d51e7bf874e5b4360fa77b7e2075
userid: hennevogel
- broken: false
comment: checked in
commit_time: 2009-12-16 13:38:28
expanded_srcmd5: 2a30eb0ee9c15cde957832981547ee00
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 2e774d4b44a27fe94a55f47790d30256
mtime: 1250103760
name: zsh-4.3.10-doc_intro_paths.patch
size: 1446
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: a0f91c040db93d6a49e8d85ded5e4dfd
mtime: 1255019009
name: zsh.changes
size: 15922
- md5: 26336ee303cb6d45a1ca215383c7fd05
mtime: 1255447649
name: zsh.spec
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 18d5fc82295b89ec951ed46159c0b3cd
package: zsh
project: shells
rev: 38.0
unexpanded_srcmd5: e38996d6ee694258a69fc97495196bb6
userid: autobuild
- broken: false
comment: converted link to branch
commit_time: 2010-02-19 16:57:01
expanded_srcmd5: dccb1483f5a5f181669122c1e0e30610
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: 1d2c10dfbf731be6a2702062c0a2a568
mtime: 1259777956
name: zsh.changes
size: 16076
- md5: fa3228826fb810f863c1654535e37291
mtime: 1260967109
name: zsh.spec
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 5cbb75a7f4cd6050f4b697f0cc88ce5c
package: zsh
project: shells
rev: 39.0
unexpanded_srcmd5: 52cc12fe68b1cdfcbe8a0fa9c07906a8
userid: coolo
- broken: false
comment: 'Copy from home:hmacht:branches:shells/zsh via accept of submit request
34442 revision 9.
Request was accepted with message:
reviewed okay
'
commit_time: 2010-03-12 15:15:23
expanded_srcmd5: 607bf7559344725305d62b720922cabd
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c91d2e28a2ea0da32d33342a2db37639
mtime: 1268150089
name: zsh.changes
size: 16437
- md5: fa3228826fb810f863c1654535e37291
mtime: 1260967109
name: zsh.spec
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 0b509568ee2fd25830868ce62410e255
package: zsh
project: shells
request:
creator: hmacht
number: 34442
source_package: zsh
source_project: home:hmacht:branches:shells
source_rev: '9'
state: accepted
type: submit
rev: 40.0
unexpanded_srcmd5: 2e0a04b44c0d119e7cc4772911a51b6b
userid: hennevogel
- broken: false
comment: checked in (request 34678)
commit_time: 2010-03-12 17:37:40
expanded_srcmd5: 3179a6e01338be0bb7c8cad90e8b5fe9
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: f55d29e390aec2cf50b50f13927c390b
mtime: 1240674821
name: _osc
size: 3600
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: 1d2c10dfbf731be6a2702062c0a2a568
mtime: 1259777956
name: zsh.changes
size: 16076
- md5: fa3228826fb810f863c1654535e37291
mtime: 1260967109
name: zsh.spec
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 5cbb75a7f4cd6050f4b697f0cc88ce5c
package: zsh
project: shells
request:
creator: hennevogel
number: 34678
source_package: zsh
source_project: shells
source_rev: '40'
state: accepted
type: submit
rev: 41.0
unexpanded_srcmd5: 0aa9bed6601a8a2a09d6d611778e109d
userid: autobuild
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 17.0
commit_time: 2010-03-12 17:37:41
expanded_srcmd5: 46d9a0744d987ef371b182977d6422d7
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: d41d8cd98f00b204e9800998ecf8427e
mtime: 1168904766
name: ready
size: 0
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c91d2e28a2ea0da32d33342a2db37639
mtime: 1268150089
name: zsh.changes
size: 16437
- md5: 23a0b81db63eade0296ad7e0dbb3b196
mtime: 1268411861
name: zsh.spec
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 2c5a1c06b358a6b3352811a05ef026b0
package: zsh
project: shells
rev: 41.017
unexpanded_srcmd5: 0aa9bed6601a8a2a09d6d611778e109d
userid: buildservice-autocommit
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 18.0
commit_time: 2010-03-18 16:40:26
expanded_srcmd5: 54f636fcb9daebcdf90a40185dab1a8c
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c91d2e28a2ea0da32d33342a2db37639
mtime: 1268150089
name: zsh.changes
size: 16437
- md5: 23a0b81db63eade0296ad7e0dbb3b196
mtime: 1268411861
name: zsh.spec
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: e2edeca864a6b90c3844dbc7d5dd060c
package: zsh
project: shells
rev: 41.035
unexpanded_srcmd5: 0aa9bed6601a8a2a09d6d611778e109d
userid: buildservice-autocommit
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 19.0
commit_time: 2010-07-09 11:23:19
expanded_srcmd5: 54f636fcb9daebcdf90a40185dab1a8c
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c91d2e28a2ea0da32d33342a2db37639
mtime: 1268150089
name: zsh.changes
size: 16437
- md5: 23a0b81db63eade0296ad7e0dbb3b196
mtime: 1268411861
name: zsh.spec
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: e2edeca864a6b90c3844dbc7d5dd060c
package: zsh
project: shells
rev: 41.054
unexpanded_srcmd5: 0aa9bed6601a8a2a09d6d611778e109d
userid: buildservice-autocommit
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 20.0
commit_time: 2010-07-09 14:30:34
expanded_srcmd5: 54f636fcb9daebcdf90a40185dab1a8c
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c7bbc55d7914d7c3c60329d92396f75f
mtime: 1250103759
name: zsh-4.3.10-doc.tar.bz2
size: 2690183
- md5: 9d798012a412a2ded00b345e1f17ebe4
mtime: 1259777956
name: zsh-4.3.10-doc_intro_paths.patch
size: 1856
- md5: 0bc5425cbe73759ccde3de43ec66c010
mtime: 1250103761
name: zsh-4.3.10-doc_makefile.patch
size: 1458
- md5: 6f0002251865180da40294fd73019abb
mtime: 1250103756
name: zsh-4.3.10-run-help_pager.patch
size: 526
- md5: 74c5b275544400082a1cde806c98682a
mtime: 1250103758
name: zsh-4.3.10.tar.bz2
size: 2735665
- md5: 94c26241ff78fbf63a35da99de4b5b4d
mtime: 1250103761
name: zsh-cleanup.patch
size: 1037
- md5: c91d2e28a2ea0da32d33342a2db37639
mtime: 1268150089
name: zsh.changes
size: 16437
- md5: 23a0b81db63eade0296ad7e0dbb3b196
mtime: 1268411861
name: zsh.spec
size: 5204
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: e2edeca864a6b90c3844dbc7d5dd060c
package: zsh
project: shells
rev: 41.074
unexpanded_srcmd5: 0aa9bed6601a8a2a09d6d611778e109d
userid: buildservice-autocommit
- broken: false
comment: reviewed okay
commit_time: 2011-02-11 11:49:56
expanded_srcmd5: 4299dae5ddef291b052f51316c5334df
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 44c92fe036a05ed9da5cf541e4765ad0
mtime: 1292857805
name: _service:download_url:zsh-4.3.11-doc.tar.bz2
size: 2687527
- md5: 3225c7f53b69f395e95723585d6785ed
mtime: 1292861216
name: _service:download_url:zsh-4.3.11.tar.bz2
size: 2868429
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 3c4c48fa72e6d5051d6d64c1f4f8c099
mtime: 1293588990
name: zsh.changes
size: 16824
- md5: 67ed7e6957ae59ab39233035c35d1000
mtime: 1293588991
name: zsh.spec
size: 5205
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 0beef51012acb75aae88b2f1c230c99b
package: zsh
project: shells
request:
creator: elvigia
number: 56833
source_package: zsh
source_project: home:elvigia:branches:shells
source_rev: '3'
state: accepted
type: submit
rev: 42.0
unexpanded_srcmd5: f9064698595d2c3db5f7862acf2881ff
userid: hennevogel
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 21.0
commit_time: 2011-02-17 12:18:45
expanded_srcmd5: 4299dae5ddef291b052f51316c5334df
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 44c92fe036a05ed9da5cf541e4765ad0
mtime: 1292857805
name: _service:download_url:zsh-4.3.11-doc.tar.bz2
size: 2687527
- md5: 3225c7f53b69f395e95723585d6785ed
mtime: 1292861216
name: _service:download_url:zsh-4.3.11.tar.bz2
size: 2868429
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 3c4c48fa72e6d5051d6d64c1f4f8c099
mtime: 1293588990
name: zsh.changes
size: 16824
- md5: 67ed7e6957ae59ab39233035c35d1000
mtime: 1293588991
name: zsh.spec
size: 5205
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 0beef51012acb75aae88b2f1c230c99b
package: zsh
project: shells
rev: 42.021
unexpanded_srcmd5: f9064698595d2c3db5f7862acf2881ff
userid: buildservice-autocommit
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 22.0
commit_time: 2011-03-07 15:13:58
expanded_srcmd5: 5b38feb3c16d209a656acfd0b34b9a17
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 44c92fe036a05ed9da5cf541e4765ad0
mtime: 1292857805
name: _service:download_url:zsh-4.3.11-doc.tar.bz2
size: 2687527
- md5: 3225c7f53b69f395e95723585d6785ed
mtime: 1292861216
name: _service:download_url:zsh-4.3.11.tar.bz2
size: 2868429
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 3c4c48fa72e6d5051d6d64c1f4f8c099
mtime: 1293588990
name: zsh.changes
size: 16824
- md5: 67ed7e6957ae59ab39233035c35d1000
mtime: 1293588991
name: zsh.spec
size: 5205
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 0beef51012acb75aae88b2f1c230c99b
package: zsh
project: shells
rev: 42.043
unexpanded_srcmd5: f9064698595d2c3db5f7862acf2881ff
userid: buildservice-autocommit
- broken: false
comment: 'baserev update by copy to link target
'
commit_time: 2011-03-07 15:14:00
expanded_srcmd5: ee381d97ceca0a90c58da05361cf3e5c
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 44c92fe036a05ed9da5cf541e4765ad0
mtime: 1292857805
name: _service:download_url:zsh-4.3.11-doc.tar.bz2
size: 2687527
- md5: 3225c7f53b69f395e95723585d6785ed
mtime: 1292861216
name: _service:download_url:zsh-4.3.11.tar.bz2
size: 2868429
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 3c4c48fa72e6d5051d6d64c1f4f8c099
mtime: 1293588990
name: zsh.changes
size: 16824
- md5: 67ed7e6957ae59ab39233035c35d1000
mtime: 1293588991
name: zsh.spec
size: 5205
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 0beef51012acb75aae88b2f1c230c99b
package: zsh
project: shells
request:
creator: coolo
number: 63473
source_package: zsh
source_project: shells
source_rev: null
state: accepted
type: submit
rev: 43.0
unexpanded_srcmd5: 0e31bc9fe3a7fc7d82765b296ccf7a4c
userid: buildservice-autocommit
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 23.0
commit_time: 2011-03-07 15:14:09
expanded_srcmd5: e730055b3afbaad8c7818390bc1a3000
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 44c92fe036a05ed9da5cf541e4765ad0
mtime: 1292857805
name: _service:download_url:zsh-4.3.11-doc.tar.bz2
size: 2687527
- md5: 3225c7f53b69f395e95723585d6785ed
mtime: 1292861216
name: _service:download_url:zsh-4.3.11.tar.bz2
size: 2868429
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 3c4c48fa72e6d5051d6d64c1f4f8c099
mtime: 1293588990
name: zsh.changes
size: 16824
- md5: 35d43f1d73ff413cd02c4db48ca10c46
mtime: 1299507249
name: zsh.spec
size: 5187
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: b8ee837e60f0d18c01dbd3ddb7df13ce
package: zsh
project: shells
rev: 43.023
unexpanded_srcmd5: 0e31bc9fe3a7fc7d82765b296ccf7a4c
userid: buildservice-autocommit
- broken: false
comment: 'Fix crash with '
commit_time: 2011-03-15 15:12:09
expanded_srcmd5: d895f229d16781f640bb0a08297fe752
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 0572141ef2a2c1239a8613f7600e9d5d
mtime: 1300198323
name: subst-crash.patch
size: 1100
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 5acf2fde717b866ad409b0070c0a4950
mtime: 1300198326
name: zsh.changes
size: 16972
- md5: 56893f45631ff3f8b0684783e5e53e28
mtime: 1300198329
name: zsh.spec
size: 5233
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: b146a48a44c8eb08c8758f0788ba194c
package: zsh
project: shells
rev: 44.0
unexpanded_srcmd5: c7242a4c7ae5cbbdb3f0a3a23a7ccc3f
userid: namtrac
- broken: false
comment: generated via source service
commit_time: 2011-03-15 15:13:30
expanded_srcmd5: deacb82e2dc02a86deb3ec5306c9e0df
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 44c92fe036a05ed9da5cf541e4765ad0
mtime: 1292857805
name: _service:download_url:zsh-4.3.11-doc.tar.bz2
size: 2687527
- md5: 3225c7f53b69f395e95723585d6785ed
mtime: 1292861216
name: _service:download_url:zsh-4.3.11.tar.bz2
size: 2868429
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 0572141ef2a2c1239a8613f7600e9d5d
mtime: 1300198323
name: subst-crash.patch
size: 1100
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 5acf2fde717b866ad409b0070c0a4950
mtime: 1300198326
name: zsh.changes
size: 16972
- md5: 56893f45631ff3f8b0684783e5e53e28
mtime: 1300198329
name: zsh.spec
size: 5233
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 3112f8413e243d712ecf3a76b429dbc0
package: zsh
project: shells
rev: 45.0
unexpanded_srcmd5: 684dfadf5cbb43ea8fb854cbeb220715
userid: _service
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 24.0
commit_time: 2011-03-16 11:21:24
expanded_srcmd5: 6803d299c3373805b70d26c8f61505b2
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 44c92fe036a05ed9da5cf541e4765ad0
mtime: 1292857805
name: _service:download_url:zsh-4.3.11-doc.tar.bz2
size: 2687527
- md5: 3225c7f53b69f395e95723585d6785ed
mtime: 1292861216
name: _service:download_url:zsh-4.3.11.tar.bz2
size: 2868429
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 0572141ef2a2c1239a8613f7600e9d5d
mtime: 1300198323
name: subst-crash.patch
size: 1100
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 5acf2fde717b866ad409b0070c0a4950
mtime: 1300198326
name: zsh.changes
size: 16972
- md5: 56893f45631ff3f8b0684783e5e53e28
mtime: 1300198329
name: zsh.spec
size: 5233
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 3112f8413e243d712ecf3a76b429dbc0
package: zsh
project: shells
rev: 45.024
unexpanded_srcmd5: 684dfadf5cbb43ea8fb854cbeb220715
userid: buildservice-autocommit
- broken: false
comment: 'baserev update by copy to link target
'
commit_time: 2011-03-16 11:21:25
expanded_srcmd5: f718589b369623fb2af1a5c733ec8f4a
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 44c92fe036a05ed9da5cf541e4765ad0
mtime: 1292857805
name: _service:download_url:zsh-4.3.11-doc.tar.bz2
size: 2687527
- md5: 3225c7f53b69f395e95723585d6785ed
mtime: 1292861216
name: _service:download_url:zsh-4.3.11.tar.bz2
size: 2868429
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 0572141ef2a2c1239a8613f7600e9d5d
mtime: 1300198323
name: subst-crash.patch
size: 1100
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 5acf2fde717b866ad409b0070c0a4950
mtime: 1300198326
name: zsh.changes
size: 16972
- md5: 56893f45631ff3f8b0684783e5e53e28
mtime: 1300198329
name: zsh.spec
size: 5233
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 3112f8413e243d712ecf3a76b429dbc0
package: zsh
project: shells
request:
creator: namtrac
number: 64202
source_package: zsh
source_project: shells
source_rev: null
state: accepted
type: submit
rev: 46.0
unexpanded_srcmd5: f672eab6b96871057c60bd9e32120d91
userid: buildservice-autocommit
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 25.0
commit_time: 2011-03-16 11:21:38
expanded_srcmd5: fd645d6a068ed15f44e4d42f62d3c986
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 48ca7fd144520e82711dafd88d808031
mtime: 1293588982
name: _service
size: 936
- md5: 44c92fe036a05ed9da5cf541e4765ad0
mtime: 1292857805
name: _service:download_url:zsh-4.3.11-doc.tar.bz2
size: 2687527
- md5: 3225c7f53b69f395e95723585d6785ed
mtime: 1292861216
name: _service:download_url:zsh-4.3.11.tar.bz2
size: 2868429
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 0572141ef2a2c1239a8613f7600e9d5d
mtime: 1300198323
name: subst-crash.patch
size: 1100
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 5acf2fde717b866ad409b0070c0a4950
mtime: 1300198326
name: zsh.changes
size: 16972
- md5: 4c9fa541dccbea30e2954d4af2c068bf
mtime: 1300270898
name: zsh.spec
size: 5233
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: d9699f7407eca48bb9ef9b199767dcdd
package: zsh
project: shells
rev: 46.025
unexpanded_srcmd5: f672eab6b96871057c60bd9e32120d91
userid: buildservice-autocommit
- broken: false
comment: '
- Update to 4.3.11-dev-2, many crash fixes'
commit_time: 2011-04-20 14:52:03
expanded_srcmd5: 115813ff2213c38aba6f712f066ebc11
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: ee1e63182baf367fa465836224c13a17
mtime: 1303303922
name: _service
size: 982
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: a0e096213e690517b12226ef4bd2b32c
mtime: 1303303922
name: zsh.changes
size: 17137
- md5: d84ab15e45075d37dded483904be1df1
mtime: 1303303922
name: zsh.spec
size: 4638
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: fc9cca306181c54d858f594ca72bf491
package: zsh
project: shells
rev: 47.0
unexpanded_srcmd5: bd59ad6d0d969902e6a7fa25fa99c2d6
userid: namtrac
- broken: false
comment: Spec cleanup and remove unused doc package
commit_time: 2011-04-20 14:54:27
expanded_srcmd5: 50106edbfeacaa28b5075dbd88b29df2
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: db7ed0b8e57546a9312755e45fb559e3
mtime: 1303304067
name: _service
size: 510
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: a0e096213e690517b12226ef4bd2b32c
mtime: 1303303922
name: zsh.changes
size: 17137
- md5: 7df04f49908bd8ef08575c943bc32f53
mtime: 1303304067
name: zsh.spec
size: 4494
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 932a3b9394be3092a1ff787a2bd70a14
package: zsh
project: shells
rev: 48.0
unexpanded_srcmd5: 1a2de20e869e8ab5f49b46f3f1d71fb9
userid: namtrac
- broken: false
comment: generated via source service
commit_time: 2011-04-20 14:56:53
expanded_srcmd5: 9bba4a671404180548793e8bfc082cc8
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: db7ed0b8e57546a9312755e45fb559e3
mtime: 1303304067
name: _service
size: 510
- md5: 855830a6bb7d17ef50b22f7175289ecc
mtime: 1303304212
name: _service_error
size: 5490
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: a0e096213e690517b12226ef4bd2b32c
mtime: 1303303922
name: zsh.changes
size: 17137
- md5: 7df04f49908bd8ef08575c943bc32f53
mtime: 1303304067
name: zsh.spec
size: 4494
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: deab832ec6d3e78f7aa7e450e2b7dd7c
package: zsh
project: shells
rev: 49.0
unexpanded_srcmd5: b6f53e25e4c67b2c370e2c23fd1b6051
userid: _service
- broken: false
comment: generated via source service
commit_time: 2011-04-20 15:00:58
expanded_srcmd5: 947aad98003982ac024012fa7bd87cd7
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: db7ed0b8e57546a9312755e45fb559e3
mtime: 1303304067
name: _service
size: 510
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304456
name: _service:download_url:zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: a0e096213e690517b12226ef4bd2b32c
mtime: 1303303922
name: zsh.changes
size: 17137
- md5: 7df04f49908bd8ef08575c943bc32f53
mtime: 1303304067
name: zsh.spec
size: 4494
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 710599476704dcedcd737c5c44ffd707
package: zsh
project: shells
rev: 50.0
unexpanded_srcmd5: 224a4d001036926f4d6c0ca81f7cb548
userid: _service
- broken: false
comment: Stop using service file
commit_time: 2011-04-20 15:03:12
expanded_srcmd5: dac11039f5b84af8f054b800180ccd17
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: d7023b8f3e2833dcb4027190df4095bb
mtime: 1142381833
name: _make
size: 1954
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: a0e096213e690517b12226ef4bd2b32c
mtime: 1303303922
name: zsh.changes
size: 17137
- md5: 7df04f49908bd8ef08575c943bc32f53
mtime: 1303304067
name: zsh.spec
size: 4494
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 2e03f4a0067c2fc885b2498f7f1d9bbd
package: zsh
project: shells
rev: 51.0
unexpanded_srcmd5: 7723d319dc085a4e7f9edebf9dc570a3
userid: namtrac
- broken: false
comment: Use zsh's own make completion
commit_time: 2011-04-20 15:39:42
expanded_srcmd5: 6b012313790dbff986253c883b4f17f3
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: a0e096213e690517b12226ef4bd2b32c
mtime: 1303303922
name: zsh.changes
size: 17137
- md5: c713faf3ad87a5a60f6b91ceee1f0421
mtime: 1303306782
name: zsh.spec
size: 4461
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 34e9e00ea77199d669be4871562e9b06
package: zsh
project: shells
rev: 52.0
unexpanded_srcmd5: 8e8db5bebe2cec10d4b6da8b28432b3a
userid: namtrac
- broken: false
comment: '
- Disable zsh debug
- Enable strict aliasing again'
commit_time: 2011-04-21 11:23:04
expanded_srcmd5: 2314ff98021175787c796c8541676dce
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 47e31420ebe54e2ed2c71648911eb481
mtime: 1303377783
name: zsh.changes
size: 17310
- md5: 33d1ea4ca130f137ea326e79afe5bbe1
mtime: 1303377783
name: zsh.spec
size: 4372
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: d98a4f575b0609a2cf99149937c7ae8c
package: zsh
project: shells
rev: 53.0
unexpanded_srcmd5: 448fe7f5ffcb55a4c5bd10ff16931b8a
userid: namtrac
- broken: false
comment: '
Do make check after make'
commit_time: 2011-04-21 13:49:11
expanded_srcmd5: e5565a38799abdebb3f23fcccd5b8bdc
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 47e31420ebe54e2ed2c71648911eb481
mtime: 1303377783
name: zsh.changes
size: 17310
- md5: 34cc34de1f3b1da15d96fa9e1c7d3ec6
mtime: 1303386550
name: zsh.spec
size: 4364
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 13212a3214fb96627cba6afbdc3c3300
package: zsh
project: shells
rev: 54.0
unexpanded_srcmd5: 8dfb366f942664a0f9426ad26cd3ef9a
userid: namtrac
- broken: false
comment: Disable check for now, it seems to depend on some environmental variables
commit_time: 2011-04-21 14:05:39
expanded_srcmd5: 1499ce1e704824b63db6ee91e59bb681
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 47e31420ebe54e2ed2c71648911eb481
mtime: 1303377783
name: zsh.changes
size: 17310
- md5: 478d9ea82bda7070d661b19be2207bb6
mtime: 1303387538
name: zsh.spec
size: 4373
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: dd641cece5947761352d86a44c80ccd3
package: zsh
project: shells
rev: 55.0
unexpanded_srcmd5: e9b04e975037cb4909ccf73082df4b62
userid: namtrac
- broken: false
comment: Fix license
commit_time: 2011-04-21 14:22:21
expanded_srcmd5: 83c050ed355745facafdcebf16592986
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 47e31420ebe54e2ed2c71648911eb481
mtime: 1303377783
name: zsh.changes
size: 17310
- md5: edc380a5c74744e5681dc30c4bed55d9
mtime: 1303388540
name: zsh.spec
size: 4341
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 0d85f13995ce80217916957177ca30f9
package: zsh
project: shells
rev: 56.0
unexpanded_srcmd5: ae2d4edab624243360e73d07dd7cb85a
userid: namtrac
- broken: false
comment: Disable racy tests and enable make check again
commit_time: 2011-04-21 14:48:30
expanded_srcmd5: 1113fc55aaa3a4e5bdfa03e57e059871
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: 32c24f37467c3cba835dbb1529bc0376
mtime: 1303390110
name: zsh-4.3.6-hack-a01grammar-test-select-off.patch
size: 884
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 22dde6d798210712e3ad4449434a6fc3
mtime: 1303390110
name: zsh-test-C02-dev_fd-mock.patch
size: 803
- md5: 47e31420ebe54e2ed2c71648911eb481
mtime: 1303377783
name: zsh.changes
size: 17310
- md5: d10acc71de2e437c5726a2d57c0c4cf5
mtime: 1303390110
name: zsh.spec
size: 4671
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 2fe3563aec1c41a49ec01631fc2361b4
package: zsh
project: shells
rev: 57.0
unexpanded_srcmd5: e465cb447165e12151e2f7fd792d84a1
userid: namtrac
- broken: false
comment: Typo
commit_time: 2011-04-21 14:52:14
expanded_srcmd5: 547df8ba0680b7b0ee7c3dc4b090b73e
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: 32c24f37467c3cba835dbb1529bc0376
mtime: 1303390110
name: zsh-4.3.6-hack-a01grammar-test-select-off.patch
size: 884
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 22dde6d798210712e3ad4449434a6fc3
mtime: 1303390110
name: zsh-test-C02-dev_fd-mock.patch
size: 803
- md5: 47e31420ebe54e2ed2c71648911eb481
mtime: 1303377783
name: zsh.changes
size: 17310
- md5: d6f61a64ea58258195bef0a602c7c77e
mtime: 1303390334
name: zsh.spec
size: 4675
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 8e06a8a042b1075c6663b18c2fec0d45
package: zsh
project: shells
rev: 58.0
unexpanded_srcmd5: 153bc33220ab2ff0fc100b144428fcc3
userid: namtrac
- broken: false
comment: Remove unneeded patch, disable check again
commit_time: 2011-04-21 15:08:22
expanded_srcmd5: b048dc8c2e91eb6c7dc3fa0915975d94
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: 32c24f37467c3cba835dbb1529bc0376
mtime: 1303390110
name: zsh-4.3.6-hack-a01grammar-test-select-off.patch
size: 884
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 47e31420ebe54e2ed2c71648911eb481
mtime: 1303377783
name: zsh.changes
size: 17310
- md5: 3863e4452009e304276bb907c0062a0f
mtime: 1303391302
name: zsh.spec
size: 4524
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: ee34587024b019b9d3c57e2ee788ca5c
package: zsh
project: shells
rev: 59.0
unexpanded_srcmd5: fdce17c0d0ce783547ae89ad21301ecc
userid: namtrac
- broken: false
comment: Try to fix A01grammar test
commit_time: 2011-04-21 19:39:13
expanded_srcmd5: 81a0db8d9560b2bba3a822645d2fa337
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: e3f12a27e6a4630f3ad8682b706a6b54
mtime: 1303407548
name: zsh-4.3.11-fix-a01grammar.patch
size: 386
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: 32c24f37467c3cba835dbb1529bc0376
mtime: 1303390110
name: zsh-4.3.6-hack-a01grammar-test-select-off.patch
size: 884
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 47e31420ebe54e2ed2c71648911eb481
mtime: 1303377783
name: zsh.changes
size: 17310
- md5: 14d45fbb9f9ee4dd0e24fad710de50fc
mtime: 1303407551
name: zsh.spec
size: 4565
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 92b56569bcb57a9a4f80eebf7615963c
package: zsh
project: shells
rev: 60.0
unexpanded_srcmd5: 421dbad0816ccb06a5cb318cd2fbcd30
userid: namtrac
- broken: false
comment: Fix patch tag
commit_time: 2011-04-21 19:48:17
expanded_srcmd5: bc2575d858969bc632aed2b52cd72242
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: e3f12a27e6a4630f3ad8682b706a6b54
mtime: 1303407548
name: zsh-4.3.11-fix-a01grammar.patch
size: 386
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 47e31420ebe54e2ed2c71648911eb481
mtime: 1303377783
name: zsh.changes
size: 17310
- md5: 6173a391fa6d719505718031d2802223
mtime: 1303408096
name: zsh.spec
size: 4484
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 752bff367a3e7a05b2da7ce580cdf7cd
package: zsh
project: shells
rev: 61.0
unexpanded_srcmd5: 489bf580cd17579df9c51746d0ab1b73
userid: namtrac
- broken: false
comment: ''
commit_time: 2011-04-21 20:09:58
expanded_srcmd5: a3b3132550c5357418d61e3686d8c943
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: 0bb4a66f7a2e1e55a3d441569fc66db5
mtime: 1303409398
name: zsh-4.3.11-disable-c02cond-test.patch
size: 2044
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: e3f12a27e6a4630f3ad8682b706a6b54
mtime: 1303407548
name: zsh-4.3.11-fix-a01grammar.patch
size: 386
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 47e31420ebe54e2ed2c71648911eb481
mtime: 1303377783
name: zsh.changes
size: 17310
- md5: 6173a391fa6d719505718031d2802223
mtime: 1303408096
name: zsh.spec
size: 4484
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 745bdee68a655724582ef9f69c05c56d
package: zsh
project: shells
rev: 62.0
unexpanded_srcmd5: c2277d0799ef3c49e424946715abc56b
userid: namtrac
- broken: false
comment: Disable a problematic test in c02cond test
commit_time: 2011-04-21 20:11:24
expanded_srcmd5: a9f59ccfc506549b577f9d89b242a78e
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: 0bb4a66f7a2e1e55a3d441569fc66db5
mtime: 1303409398
name: zsh-4.3.11-disable-c02cond-test.patch
size: 2044
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: e3f12a27e6a4630f3ad8682b706a6b54
mtime: 1303407548
name: zsh-4.3.11-fix-a01grammar.patch
size: 386
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 47e31420ebe54e2ed2c71648911eb481
mtime: 1303377783
name: zsh.changes
size: 17310
- md5: 92a669ef8c7b9577048c51f250b2d54c
mtime: 1303409484
name: zsh.spec
size: 4658
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 92e5854316d9d9feea3ef221b3b3aaae
package: zsh
project: shells
rev: 63.0
unexpanded_srcmd5: 4540eed3cd72e4dfd7dc81a768a29c6c
userid: namtrac
- broken: false
comment: ''
commit_time: 2011-04-21 20:22:23
expanded_srcmd5: a17536fc49e6ad7f04e738d77be8e4ea
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: e3f12a27e6a4630f3ad8682b706a6b54
mtime: 1303407548
name: zsh-4.3.11-fix-a01grammar.patch
size: 386
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 47e31420ebe54e2ed2c71648911eb481
mtime: 1303377783
name: zsh.changes
size: 17310
- md5: 92a669ef8c7b9577048c51f250b2d54c
mtime: 1303409484
name: zsh.spec
size: 4658
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 58458187616e66936336209c8287cdfe
package: zsh
project: shells
rev: 64.0
unexpanded_srcmd5: 8220e8a23117df8b237b624bec640d42
userid: namtrac
- broken: false
comment: ''
commit_time: 2011-04-21 20:22:39
expanded_srcmd5: 54f2782c7e2a78092e6a027584349157
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: 04b864452ce11f5432b452e37220ed99
mtime: 1303410159
name: zsh-4.3.11-disable-c02cond-test.patch
size: 409
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: e3f12a27e6a4630f3ad8682b706a6b54
mtime: 1303407548
name: zsh-4.3.11-fix-a01grammar.patch
size: 386
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: 47e31420ebe54e2ed2c71648911eb481
mtime: 1303377783
name: zsh.changes
size: 17310
- md5: 92a669ef8c7b9577048c51f250b2d54c
mtime: 1303409484
name: zsh.spec
size: 4658
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 46d78dc38930d46fe491edcaa41c53fe
package: zsh
project: shells
rev: 65.0
unexpanded_srcmd5: 5af6b9384700b585802ee347664b6f44
userid: namtrac
- broken: false
comment: '
- Enable make check'
commit_time: 2011-04-26 17:46:22
expanded_srcmd5: 3f383ba2c69ceee6f627ab2f0e404c30
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: 04b864452ce11f5432b452e37220ed99
mtime: 1303410159
name: zsh-4.3.11-disable-c02cond-test.patch
size: 409
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: e3f12a27e6a4630f3ad8682b706a6b54
mtime: 1303407548
name: zsh-4.3.11-fix-a01grammar.patch
size: 386
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: e7ca2b955593216ff1ce9937318b83e5
mtime: 1303832781
name: zsh.changes
size: 17452
- md5: 92a669ef8c7b9577048c51f250b2d54c
mtime: 1303409484
name: zsh.spec
size: 4658
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 587abcb76f5eb1274f152ad63f77c3e7
package: zsh
project: shells
rev: 66.0
unexpanded_srcmd5: ebbf2d27084bc313c66908af7328ddbc
userid: namtrac
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 26.0
commit_time: 2011-04-29 09:15:29
expanded_srcmd5: 964292ef83b17d3c163ccb46078fc9b4
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: 04b864452ce11f5432b452e37220ed99
mtime: 1303410159
name: zsh-4.3.11-disable-c02cond-test.patch
size: 409
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: e3f12a27e6a4630f3ad8682b706a6b54
mtime: 1303407548
name: zsh-4.3.11-fix-a01grammar.patch
size: 386
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: e7ca2b955593216ff1ce9937318b83e5
mtime: 1303832781
name: zsh.changes
size: 17452
- md5: 92a669ef8c7b9577048c51f250b2d54c
mtime: 1303409484
name: zsh.spec
size: 4658
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 587abcb76f5eb1274f152ad63f77c3e7
package: zsh
project: shells
rev: 66.026
unexpanded_srcmd5: ebbf2d27084bc313c66908af7328ddbc
userid: buildservice-autocommit
- broken: false
comment: baserev update by copy to link target
commit_time: 2011-04-29 09:15:31
expanded_srcmd5: 169b5c928fb2afb62d94ef0ad7fc6efa
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: 04b864452ce11f5432b452e37220ed99
mtime: 1303410159
name: zsh-4.3.11-disable-c02cond-test.patch
size: 409
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: e3f12a27e6a4630f3ad8682b706a6b54
mtime: 1303407548
name: zsh-4.3.11-fix-a01grammar.patch
size: 386
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: e7ca2b955593216ff1ce9937318b83e5
mtime: 1303832781
name: zsh.changes
size: 17452
- md5: 92a669ef8c7b9577048c51f250b2d54c
mtime: 1303409484
name: zsh.spec
size: 4658
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 587abcb76f5eb1274f152ad63f77c3e7
package: zsh
project: shells
request:
creator: namtrac
number: 68403
source_package: zsh
source_project: shells
source_rev: '66'
state: accepted
type: submit
rev: 67.0
unexpanded_srcmd5: 474a2762ce55298659c3b8c72778fb8d
userid: buildservice-autocommit
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 27.0
commit_time: 2011-04-29 09:15:42
expanded_srcmd5: 69c2f52bd11fa07eb9b98886d3d27101
files:
- md5: 0f8d3ca1286bea7eee4eb96583191524
mtime: 1142381833
name: _SuSEconfig
size: 582
- md5: 1ee7a476f798586967acf506e04a257c
mtime: 1142381832
name: _hwinfo
size: 1917
- md5: 5f65f63c58c4cc6ce0928aa83705b1a1
mtime: 1268154003
name: _osc
size: 4146
- md5: 25561eaa748990a394d280defb8bf584
mtime: 1142381834
name: _yast2
size: 819
- md5: 245560a667546e43210e1a990d04a8db
mtime: 1240520479
name: _zypper
size: 2041
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: 5512e3af6b6e870cca86242d8f03c05f
mtime: 1303304592
name: zsh-4.3.11-dev-2.tar.bz2
size: 2903987
- md5: 04b864452ce11f5432b452e37220ed99
mtime: 1303410159
name: zsh-4.3.11-disable-c02cond-test.patch
size: 409
- md5: c496de508ab144ea79b7c13ae7883663
mtime: 1293588983
name: zsh-4.3.11-doc_intro_paths.patch
size: 1528
- md5: 1a68ebf71d6346de568c4c698fa0c2fa
mtime: 1293588985
name: zsh-4.3.11-doc_makefile.patch
size: 1524
- md5: e3f12a27e6a4630f3ad8682b706a6b54
mtime: 1303407548
name: zsh-4.3.11-fix-a01grammar.patch
size: 386
- md5: aa8a7434313606bad66e41a9c09f05c4
mtime: 1293588986
name: zsh-4.3.11-run-help_pager.patch
size: 539
- md5: f9433d21f2330635150d7705225c6085
mtime: 1293588988
name: zsh-cleanup.patch
size: 1081
- md5: e7ca2b955593216ff1ce9937318b83e5
mtime: 1303832781
name: zsh.changes
size: 17452
- md5: 467b540e277d60f820f78c083bd299f1
mtime: 1304061342
name: zsh.spec
size: 4672
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 0aaf34df42f0f8ac44ba191256492684
package: zsh
project: shells
rev: 67.027
unexpanded_srcmd5: 474a2762ce55298659c3b8c72778fb8d
userid: buildservice-autocommit
- broken: false
comment: Update to final 4.3.12 release
commit_time: 2011-06-01 15:20:56
expanded_srcmd5: 242a2ff2ccc47dcd67c2d719a8392d7a
files:
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: ec6cf64299ecd82c294396e1f70a5698
mtime: 1306934290
name: zsh.changes
size: 17596
- md5: e2c3b46c96f6a334cac10452babd0914
mtime: 1306164758
name: zsh.spec
size: 3731
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 3a28a0afb9862957325ea971a3842e81
package: zsh
project: shells
request:
creator: namtrac
number: 72432
source_package: zsh
source_project: home:namtrac:branches:shells
source_rev: '6'
state: accepted
type: submit
rev: 68.0
unexpanded_srcmd5: 11db5e192e459648b4300978eff2daf4
userid: namtrac
- broken: false
comment: Update changes file
commit_time: 2011-06-01 15:36:24
expanded_srcmd5: 48793f736858f78092ed2245fceb80f2
files:
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: 4869467391046af289e6cf0acfc4be1d
mtime: 1306935383
name: zsh.changes
size: 17660
- md5: e2c3b46c96f6a334cac10452babd0914
mtime: 1306164758
name: zsh.spec
size: 3731
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 963a9d04d6a12596fdac68d85449547e
package: zsh
project: shells
rev: 69.0
unexpanded_srcmd5: 4d13c0246b3b8699c20880a8c3492ff4
userid: namtrac
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 28.0
commit_time: 2011-06-06 13:16:02
expanded_srcmd5: 197f7a22b5b16c42ac669fffd0966d30
files:
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: 4869467391046af289e6cf0acfc4be1d
mtime: 1306935383
name: zsh.changes
size: 17660
- md5: e2c3b46c96f6a334cac10452babd0914
mtime: 1306164758
name: zsh.spec
size: 3731
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 963a9d04d6a12596fdac68d85449547e
package: zsh
project: shells
rev: 69.028
unexpanded_srcmd5: 4d13c0246b3b8699c20880a8c3492ff4
userid: buildservice-autocommit
- broken: false
comment: baserev update by copy to link target
commit_time: 2011-06-06 13:16:06
expanded_srcmd5: f25338b42aa22e955572f1063b7ceab8
files:
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: 4869467391046af289e6cf0acfc4be1d
mtime: 1306935383
name: zsh.changes
size: 17660
- md5: e2c3b46c96f6a334cac10452babd0914
mtime: 1306164758
name: zsh.spec
size: 3731
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 963a9d04d6a12596fdac68d85449547e
package: zsh
project: shells
request:
creator: namtrac
number: 72437
source_package: zsh
source_project: shells
source_rev: '69'
state: accepted
type: submit
rev: 70.0
unexpanded_srcmd5: 221b157375c59a2d9dc0dadc90146895
userid: buildservice-autocommit
- broken: false
comment: "- Add zsh-kill-suspended-job.patch: fix killing suspended jobs \n- Add\
\ zsh-findproc.patch: fix findproc() to find stopped jobs"
commit_time: 2011-06-17 15:42:26
expanded_srcmd5: 2cddd695552913bff7a254d431f803f2
files:
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 53450d7cc95c0b906ee900cabb9934ac
mtime: 1308318146
name: zsh.changes
size: 17906
- md5: a66d9fc153c15122a6c390fe67fdc2cc
mtime: 1308318146
name: zsh.spec
size: 4089
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 13cdb1e0c6f7b2cb361254b4e9310c05
package: zsh
project: shells
rev: 71.0
unexpanded_srcmd5: 4b67805e7c026eec8ed284d12baf4dc8
userid: namtrac
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 29.0
commit_time: 2011-06-20 11:00:45
expanded_srcmd5: 5b5a86aa25ddf9ede15f958c04fc0a7e
files:
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 53450d7cc95c0b906ee900cabb9934ac
mtime: 1308318146
name: zsh.changes
size: 17906
- md5: a66d9fc153c15122a6c390fe67fdc2cc
mtime: 1308318146
name: zsh.spec
size: 4089
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 13cdb1e0c6f7b2cb361254b4e9310c05
package: zsh
project: shells
rev: 71.029
unexpanded_srcmd5: 4b67805e7c026eec8ed284d12baf4dc8
userid: buildservice-autocommit
- broken: false
comment: baserev update by copy to link target
commit_time: 2011-06-20 11:00:48
expanded_srcmd5: 5d4be3aa6181b33c81dcd1568a31b901
files:
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 53450d7cc95c0b906ee900cabb9934ac
mtime: 1308318146
name: zsh.changes
size: 17906
- md5: a66d9fc153c15122a6c390fe67fdc2cc
mtime: 1308318146
name: zsh.spec
size: 4089
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 13cdb1e0c6f7b2cb361254b4e9310c05
package: zsh
project: shells
request:
creator: namtrac
number: 74050
source_package: zsh
source_project: shells
source_rev: '71'
state: accepted
type: submit
rev: 72.0
unexpanded_srcmd5: 370d2561e4ffd90dc291dd2b545cc6a1
userid: buildservice-autocommit
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 30.0
commit_time: 2011-06-20 11:00:57
expanded_srcmd5: 18825818663481effd11a367187fa1fe
files:
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 53450d7cc95c0b906ee900cabb9934ac
mtime: 1308318146
name: zsh.changes
size: 17906
- md5: 57f7c2bc180e86c11399a4cf1f7c9f4a
mtime: 1308560457
name: zsh.spec
size: 4089
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
files_hash: 2cd199f053e43c33c01e830e43a7f24a
package: zsh
project: shells
rev: 72.03
unexpanded_srcmd5: 370d2561e4ffd90dc291dd2b545cc6a1
userid: buildservice-autocommit
- broken: false
comment: enable build for CentOS, fix deps for fdupes
commit_time: 2011-06-29 16:02:48
expanded_srcmd5: a839df6b8a92c2e8b44518fa4c24b09d
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309349171
name: dotzshrc
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: e36c6800e5f3b0f61fee5bda9cc7bcff
mtime: 1309351072
name: zsh.changes
size: 18302
- md5: 8fb2926edd42a8c6bc1745435725084b
mtime: 1309351073
name: zsh.spec
size: 7953
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 6f8098301c776b87f026bc57705453a6
package: zsh
project: shells
request:
creator: computersalat
number: 74829
source_package: zsh
source_project: home:computersalat:branches:shells
source_rev: '4'
state: accepted
type: submit
rev: 73.0
unexpanded_srcmd5: 9fbad453b38f398ac465fde966cabe5f
userid: namtrac
- broken: false
comment: rename Source
commit_time: 2011-06-29 19:07:49
expanded_srcmd5: 25bade79926d5c47b0b0a1eba56e4985
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: e36c6800e5f3b0f61fee5bda9cc7bcff
mtime: 1309351072
name: zsh.changes
size: 18302
- md5: a5434f984ab588eb343d6d10b6533169
mtime: 1309365133
name: zsh.spec
size: 7956
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 0ab4372cf9ee076dadbf5498f91ff16d
package: zsh
project: shells
request:
creator: computersalat
number: 74838
source_package: zsh
source_project: home:computersalat:branches:shells
source_rev: '2'
state: accepted
type: submit
rev: 74.0
unexpanded_srcmd5: 1dd57273a6513c99646d035c01cb3850
userid: namtrac
- broken: false
comment: "- Enable pcre module \n- Build against ncurses6w instead of plain old\
\ ncurses5"
commit_time: 2011-08-03 09:21:53
expanded_srcmd5: 9d79efebef4cbb182cb93a7ca5b3f2db
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 13fb916523341afc7a37232ee386d115
mtime: 1312240671
name: zsh.changes
size: 18506
- md5: 9de5cb3d353fbe5d882984dd620420b4
mtime: 1312240672
name: zsh.spec
size: 8151
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 3bae3852ddedc66ed759ae5392001ac0
package: zsh
project: shells
request:
creator: elvigia
number: 77731
source_package: zsh
source_project: home:elvigia:branches:shells
source_rev: '2'
state: accepted
type: submit
rev: 75.0
unexpanded_srcmd5: d789976639216c9fef7de0f1245c942f
userid: namtrac
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 31.0
commit_time: 2011-08-03 10:57:44
expanded_srcmd5: 5ba8bf3c38a86472bf3c1997f0ba2e2b
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 13fb916523341afc7a37232ee386d115
mtime: 1312240671
name: zsh.changes
size: 18506
- md5: 9de5cb3d353fbe5d882984dd620420b4
mtime: 1312240672
name: zsh.spec
size: 8151
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 3bae3852ddedc66ed759ae5392001ac0
package: zsh
project: shells
rev: 75.031
unexpanded_srcmd5: d789976639216c9fef7de0f1245c942f
userid: buildservice-autocommit
- broken: false
comment: baserev update by copy to link target
commit_time: 2011-08-03 10:57:47
expanded_srcmd5: 55f7b9865c686607c460081c20e662f4
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 13fb916523341afc7a37232ee386d115
mtime: 1312240671
name: zsh.changes
size: 18506
- md5: 9de5cb3d353fbe5d882984dd620420b4
mtime: 1312240672
name: zsh.spec
size: 8151
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 3bae3852ddedc66ed759ae5392001ac0
package: zsh
project: shells
request:
creator: namtrac
number: 77747
source_package: zsh
source_project: shells
source_rev: '75'
state: accepted
type: submit
rev: 76.0
unexpanded_srcmd5: a2c28d628e2e6c4e104177513d5496b6
userid: buildservice-autocommit
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 32.0
commit_time: 2011-08-03 10:57:54
expanded_srcmd5: f275b06eac4c9b9d4cbc08fbe8b5db03
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 13fb916523341afc7a37232ee386d115
mtime: 1312240671
name: zsh.changes
size: 18506
- md5: 6c5616776cb2bb6923054fe425de691c
mtime: 1312361874
name: zsh.spec
size: 8151
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
name: zshrc
size: 6919
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 478eb7f1233ae6fef2e802733316ca10
package: zsh
project: shells
rev: 76.032
unexpanded_srcmd5: a2c28d628e2e6c4e104177513d5496b6
userid: buildservice-autocommit
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 33.0
commit_time: 2011-10-21 09:37:28
expanded_srcmd5: f275b06eac4c9b9d4cbc08fbe8b5db03
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 13fb916523341afc7a37232ee386d115
mtime: 1312240671
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 18506
- md5: 6c5616776cb2bb6923054fe425de691c
mtime: 1312361874
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8151
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b49fb18f0e3a9f6c32530ae823b07bd9
mtime: 1196723014
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 6919
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 478eb7f1233ae6fef2e802733316ca10
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 76.065
unexpanded_srcmd5: a2c28d628e2e6c4e104177513d5496b6
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Add custom completion support via /etc/zsh_completion.d \n- Fix build\
\ with new ncurses library"
commit_time: 2011-11-24 11:22:24
expanded_srcmd5: d21623a2200814d07507d65c5edd1756
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 83ae5eda450d00467008f00eafc1f92d
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 18720
- md5: 109efda15270af5065870938793d9262
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8370
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: d2dea0913a3375e4537a985ba7348f2a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 77.0
unexpanded_srcmd5: d203aee55924589dc6aa93844bbb24b5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 34.0
commit_time: 2011-11-25 11:21:37
expanded_srcmd5: ed6a09931b7129937901daff3965a4e5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 83ae5eda450d00467008f00eafc1f92d
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 18720
- md5: 109efda15270af5065870938793d9262
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8370
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: d2dea0913a3375e4537a985ba7348f2a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 77.034
unexpanded_srcmd5: d203aee55924589dc6aa93844bbb24b5
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: generated via source service
commit_time: 2011-11-25 11:21:38
expanded_srcmd5: 057f4a1fe1483bf44d34a912815452a2
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 83ae5eda450d00467008f00eafc1f92d
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 18720
- md5: 109efda15270af5065870938793d9262
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8370
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: d2dea0913a3375e4537a985ba7348f2a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 78.0
unexpanded_srcmd5: f88158a9138751c6d76c7c172e5a00b3
userid: _service
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2011-11-25 11:21:40
expanded_srcmd5: 057f4a1fe1483bf44d34a912815452a2
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 7a82c0bf0635e046ca4e9ec1bdef3811
mtime: 1306934290
name: zsh-4.3.12.tar.bz2
size: 2917959
- md5: b8d8371c2e9107788acb6a1263ae2485
mtime: 1308318145
name: zsh-findproc.patch
size: 698
- md5: 8e381dd69a253a8718f46a75151a377e
mtime: 1308318146
name: zsh-kill-suspended-job.patch
size: 1444
- md5: 83ae5eda450d00467008f00eafc1f92d
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 18720
- md5: 109efda15270af5065870938793d9262
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8370
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: d2dea0913a3375e4537a985ba7348f2a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
request:
creator: namtrac
number: 93396
source_package: zsh
source_project: shells
source_rev: '77'
state: accepted
type: submit
rev: 79.0
unexpanded_srcmd5: f88158a9138751c6d76c7c172e5a00b3
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to 4.2.12-test3\n * See included ChangeLog"
commit_time: 2011-11-28 09:43:12
expanded_srcmd5: 1ac12eb5df2afb215fe14d5e851c1655
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 03b6f17c0de0f341d9d5db568d0b360c
mtime: 1322469791
name: zsh-4.3.12-test-3.tar.bz2
size: 2965438
- md5: c438b63394ac46ee9e8cc334e1008bb5
mtime: 1322469791
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 18980
- md5: 6fbd391f67982751233c18fa36f7b385
mtime: 1322469792
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7966
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: acb09a6c37b4a8cce4130640b7cd4e28
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 80.0
unexpanded_srcmd5: 35d0fb591942bf5880d3e59da7951b19
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Cleanup spec file
- Make /bin/zsh a symlink to /usr/bin/zsh'
commit_time: 2011-11-29 15:19:15
expanded_srcmd5: 1a50472282189e163c6b70d60e82fc2b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bcebb389852767f3f5f89f3a978cfef3
mtime: 1309349172
name: zsh-4.3.12-ksh-emulation-syntax-checking.patch
size: 553
- md5: 03b6f17c0de0f341d9d5db568d0b360c
mtime: 1322469791
name: zsh-4.3.12-test-3.tar.bz2
size: 2965438
- md5: cfba3ee3adda21ce9c1c71454bf3e559
mtime: 1322576355
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 19160
- md5: 8fc05c469ab9c4ae15048064a42fb652
mtime: 1322576355
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7892
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: 375b5656e29bcbf691e2a5c901dc408f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 81.0
unexpanded_srcmd5: a097434fe1362090190b4aeeb50a0e28
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to zsh 4.2.13\n * See included ChangeLog for details\n- Drop\
\ zsh-4.3.12-ksh-emulation-syntax-checking.patch, \n fixed upstream"
commit_time: 2011-11-30 22:53:20
expanded_srcmd5: 968840f0701817fc30d211245564f707
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5b95e276b6344776cffa01edebfe606d
mtime: 1322690000
name: zsh-4.3.13.tar.bz2
size: 2964918
- md5: 6feadbf4ccf03438ce274e56779cbad0
mtime: 1322690000
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 19413
- md5: 6c1808fce1765816716c2535a5c45227
mtime: 1322690000
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7698
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: 5f471d86c7158aa41d46e0761ddda37d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 82.0
unexpanded_srcmd5: ba5dc59d1bdce546082bdf46f877e854
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
comment: '-'
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2011-12-01 08:08:25
expanded_srcmd5: 5f236845d97935d285ca7d79b464637b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5b95e276b6344776cffa01edebfe606d
mtime: 1322690000
name: zsh-4.3.13.tar.bz2
size: 2964918
- md5: bde193d0393f45119e09645b1771e3f4
mtime: 1322723305
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 19539
- md5: 6c1808fce1765816716c2535a5c45227
mtime: 1322690000
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7698
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: 08fd35a18b5bdff9d8e211a9fa886e5a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 83.0
unexpanded_srcmd5: 28fbe363fedf16eb33bd3310aa683d69
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Whoops
commit_time: 2011-12-01 11:15:53
expanded_srcmd5: 692d00c946065fb6a41873f063de65dd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 5b95e276b6344776cffa01edebfe606d
mtime: 1322690000
name: zsh-4.3.13.tar.bz2
size: 2964918
- md5: 90bde02af9623ba6c42b8068f074b933
mtime: 1322734553
name: zsh.changes
size: 19539
- md5: 6c1808fce1765816716c2535a5c45227
mtime: 1322690000
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7698
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: a0c04870d23cf557e3c5e5c51144a462
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 84.0
unexpanded_srcmd5: 9cd2db8cc802e3edc9ee758058a732d6
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 35.0
commit_time: 2011-12-01 17:39:37
expanded_srcmd5: 2d849e645f97e908efdf445785456c10
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 5b95e276b6344776cffa01edebfe606d
mtime: 1322690000
name: zsh-4.3.13.tar.bz2
size: 2964918
- md5: 90bde02af9623ba6c42b8068f074b933
mtime: 1322734553
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 19539
- md5: 6c1808fce1765816716c2535a5c45227
mtime: 1322690000
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7698
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: a0c04870d23cf557e3c5e5c51144a462
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 84.035
unexpanded_srcmd5: 9cd2db8cc802e3edc9ee758058a732d6
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: generated via source service
commit_time: 2011-12-01 17:39:38
expanded_srcmd5: 7e59e1e7b502a0f7fcbc74cb38db49a8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 5b95e276b6344776cffa01edebfe606d
mtime: 1322690000
name: zsh-4.3.13.tar.bz2
size: 2964918
- md5: 90bde02af9623ba6c42b8068f074b933
mtime: 1322734553
name: zsh.changes
size: 19539
- md5: 6c1808fce1765816716c2535a5c45227
mtime: 1322690000
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7698
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: a0c04870d23cf557e3c5e5c51144a462
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 85.0
unexpanded_srcmd5: 453f5448300acbe964e0c2a2e16041ba
userid: _service
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2011-12-01 17:39:40
expanded_srcmd5: 7e59e1e7b502a0f7fcbc74cb38db49a8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 5b95e276b6344776cffa01edebfe606d
mtime: 1322690000
name: zsh-4.3.13.tar.bz2
size: 2964918
- md5: 90bde02af9623ba6c42b8068f074b933
mtime: 1322734553
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 19539
- md5: 6c1808fce1765816716c2535a5c45227
mtime: 1322690000
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7698
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: a0c04870d23cf557e3c5e5c51144a462
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 94661
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '84'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 86.0
unexpanded_srcmd5: 453f5448300acbe964e0c2a2e16041ba
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Fix license to be MIT, zsh seems to be using the \"Modern\" variant\n\
\ of the license text.\n- Import git commits 74eed99c312de05e19b54ba6b5d37a0aeb4ba713\
\ and\n 724fd07a67f135c74eba57e9f25fd342201ec722\n * metafy() added null termination\
\ even if buffer was not modifiable\n * Fix uninitialised memory after lexer\
\ realloc"
commit_time: 2011-12-05 10:43:11
expanded_srcmd5: f30da97620875d44b0cc157f1a3f73f7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: f43dbebed4e9233728f68d6b8ddbdd8c
mtime: 1323078190
name: 724fd07a67f135c74eba57e9f25fd342201ec722.patch
size: 880
- md5: 5798131acbfbfd0240e9f1d75e99ffda
mtime: 1323078191
name: 74eed99c312de05e19b54ba6b5d37a0aeb4ba713.patch
size: 776
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 5b95e276b6344776cffa01edebfe606d
mtime: 1322690000
name: zsh-4.3.13.tar.bz2
size: 2964918
- md5: 45c764366191fa93bbb9d6ae434429f7
mtime: 1323078191
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 19977
- md5: fead4e7b40958b4be340ce5e2e40bb33
mtime: 1323078191
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7873
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 1ee6999917eee506c250445469f5e3d5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 87.0
unexpanded_srcmd5: 13ec8d17015e3f862ef0fb5747815e89
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to zsh 4.3.14\n * Drop 74eed99c312de05e19b54ba6b5d37a0aeb4ba713.patch\
\ and\n 724fd07a67f135c74eba57e9f25fd342201ec722.patch, fixed upstream\n *\
\ Fix for nanosecond timestamp support"
commit_time: 2011-12-07 14:34:12
expanded_srcmd5: 53bcd152b80d923f995090bcf9a10e45
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 1c819a3ff7302b42eba988e333e76109
mtime: 1323264851
name: zsh-4.3.14.tar.bz2
size: 2965367
- md5: 6a0212ec04e4acc8916e52853afa2309
mtime: 1323264851
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 20286
- md5: 380c043c9b9361cdccc486be74b7e682
mtime: 1323264851
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7698
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: f596979a163983240e76021b5f48c207
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 88.0
unexpanded_srcmd5: 8e9b131aea70c3fbe701d26067564318
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to zsh 4.3.15\n * Fix POSIX compatibility"
commit_time: 2011-12-20 10:33:57
expanded_srcmd5: 732ff0908dbe7831a1ea57197f13210b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: 7727cd1dcec15fac64c79f8d1bbd6d86
mtime: 1324373637
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 20455
- md5: 2d6e7212fee362db62bc64b77abc56e0
mtime: 1324373637
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7582
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshenv
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 526dc8167967e1a02cfea944271c323a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 89.0
unexpanded_srcmd5: d2890d674077b9d7058009b0b430d419
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '-'
commit_time: 2011-12-20 10:35:55
expanded_srcmd5: f1732f87655789a1f0f2ea4b2dd61f5b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b70f63d412c67775e81bbe7f9697ab96
mtime: 1305971657
name: zsh-4.3.12-disable-c02cond-test.patch
size: 375
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: 7727cd1dcec15fac64c79f8d1bbd6d86
mtime: 1324373637
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 20455
- md5: 4719270411956b74c52f6324f3915870
mtime: 1324373755
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7513
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 9e48a6012654b6c4e51c516c06649692
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 90.0
unexpanded_srcmd5: 1a7fdbbd547ab28ec3b8fd6149a7343c
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Instead of disabling c02cond manually, add upstream patch to\n automatically\
\ disable it on noatime mounted systems."
commit_time: 2011-12-31 11:48:20
expanded_srcmd5: 371cfc6f004372ee45410bfba9e7f472
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 5d5c8e88ce1631b3337a9a4444c009d9
mtime: 1325328500
name: zsh-4.3.12-fix-c02cond-test.patch
size: 812
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: 8d0c3a09b485c086e01562d8da598a5e
mtime: 1325328500
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 20691
- md5: 30408d6d3bbc8e807ab4035f66e8ba00
mtime: 1325328500
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7585
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: c62f8c1a3968b2838e03d7f60ca0726e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 91.0
unexpanded_srcmd5: 2836535cc62bf63aca7eca59029775f5
userid: namtrac
- broken: true
comment: Updating link to change in openSUSE:Factory/zsh revision 36.0
commit_time: 2012-01-04 07:33:12
expanded_srcmd5: null
files: []
files_hash: null
package: zsh
project: shells
rev: 91.036
unexpanded_srcmd5: 2836535cc62bf63aca7eca59029775f5
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: generated via source service
commit_time: 2012-01-04 07:33:12
expanded_srcmd5: 2f9d2234996e34e424715474ef172959
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 5d5c8e88ce1631b3337a9a4444c009d9
mtime: 1325328500
name: zsh-4.3.12-fix-c02cond-test.patch
size: 812
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: 8d0c3a09b485c086e01562d8da598a5e
mtime: 1325328500
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 20691
- md5: 30408d6d3bbc8e807ab4035f66e8ba00
mtime: 1325328500
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7585
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: c62f8c1a3968b2838e03d7f60ca0726e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 92.0
unexpanded_srcmd5: a497621bdf43658026e4e31c67907895
userid: _service
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2012-01-04 07:33:15
expanded_srcmd5: 2f9d2234996e34e424715474ef172959
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 5d5c8e88ce1631b3337a9a4444c009d9
mtime: 1325328500
name: zsh-4.3.12-fix-c02cond-test.patch
size: 812
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: 8d0c3a09b485c086e01562d8da598a5e
mtime: 1325328500
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 20691
- md5: 30408d6d3bbc8e807ab4035f66e8ba00
mtime: 1325328500
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7585
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: c62f8c1a3968b2838e03d7f60ca0726e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
request:
creator: namtrac
number: 97159
source_package: zsh
source_project: shells
source_rev: '90'
state: accepted
type: submit
rev: 93.0
unexpanded_srcmd5: a497621bdf43658026e4e31c67907895
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: 'I hope this is what you wanted
I didn''t changed the *.changes
this patch provides new osc completion functions for the new opensuse versions.
Also I removed old opensuse versions'
commit_time: 2012-01-31 12:04:28
expanded_srcmd5: 66cf2fcb008f31a911f86895ab61857c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: b466c94d21935ad71254e78ef7aa3b5e
mtime: 1324925887
name: osc.patch
size: 1523
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 5d5c8e88ce1631b3337a9a4444c009d9
mtime: 1325328500
name: zsh-4.3.12-fix-c02cond-test.patch
size: 812
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: 8d0c3a09b485c086e01562d8da598a5e
mtime: 1325328500
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 20691
- md5: 5fc2e90171ffb74561a3de2dc7f096d5
mtime: 1328007139
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7624
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 984fad7fb84b405f5f5aa4c026ab8baa
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
request:
creator: seilerphilipp
number: 102182
source_package: zsh
source_project: home:seilerphilipp
source_rev: '2'
state: accepted
type: submit
rev: 94.0
unexpanded_srcmd5: 5b13f3b136e6310b934cd3cb0bb91825
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Update _osc completion'
commit_time: 2012-01-31 12:08:01
expanded_srcmd5: 203d7ea95d4f30a1fbeeab7ec4548317
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: b466c94d21935ad71254e78ef7aa3b5e
mtime: 1324925887
name: osc.patch
size: 1523
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 5d5c8e88ce1631b3337a9a4444c009d9
mtime: 1325328500
name: zsh-4.3.12-fix-c02cond-test.patch
size: 812
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: 551371c36b59aacc511daa3e4902d738
mtime: 1328008081
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 20835
- md5: ce41c88feaa37c268b80dfc615d508c3
mtime: 1328008081
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7622
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: a9debeaf63ecb65a4b2bb790137896d6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 95.0
unexpanded_srcmd5: a13ad47d74a9f28440a9d236766d1c35
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 37.0
commit_time: 2012-02-01 10:01:22
expanded_srcmd5: 487912d96db7fb7441dead5ef4b4e1fc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: b466c94d21935ad71254e78ef7aa3b5e
mtime: 1324925887
name: osc.patch
size: 1523
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 5d5c8e88ce1631b3337a9a4444c009d9
mtime: 1325328500
name: zsh-4.3.12-fix-c02cond-test.patch
size: 812
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: 551371c36b59aacc511daa3e4902d738
mtime: 1328008081
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 20835
- md5: ce41c88feaa37c268b80dfc615d508c3
mtime: 1328008081
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7622
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: a9debeaf63ecb65a4b2bb790137896d6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 95.037
unexpanded_srcmd5: a13ad47d74a9f28440a9d236766d1c35
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: generated via source service
commit_time: 2012-02-01 10:01:24
expanded_srcmd5: 322fc6f9ab4601d6c2410c28a87d830f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: b466c94d21935ad71254e78ef7aa3b5e
mtime: 1324925887
name: osc.patch
size: 1523
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 5d5c8e88ce1631b3337a9a4444c009d9
mtime: 1325328500
name: zsh-4.3.12-fix-c02cond-test.patch
size: 812
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: 551371c36b59aacc511daa3e4902d738
mtime: 1328008081
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 20835
- md5: ce41c88feaa37c268b80dfc615d508c3
mtime: 1328008081
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7622
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: a9debeaf63ecb65a4b2bb790137896d6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 96.0
unexpanded_srcmd5: c37bbf80200c004112390191c5e2754c
userid: _service
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2012-02-01 10:01:25
expanded_srcmd5: 322fc6f9ab4601d6c2410c28a87d830f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: b466c94d21935ad71254e78ef7aa3b5e
mtime: 1324925887
name: osc.patch
size: 1523
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 5d5c8e88ce1631b3337a9a4444c009d9
mtime: 1325328500
name: zsh-4.3.12-fix-c02cond-test.patch
size: 812
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: 551371c36b59aacc511daa3e4902d738
mtime: 1328008081
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 20835
- md5: ce41c88feaa37c268b80dfc615d508c3
mtime: 1328008081
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7622
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: a9debeaf63ecb65a4b2bb790137896d6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 102187
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: shells
source_rev: '95'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 97.0
unexpanded_srcmd5: c37bbf80200c004112390191c5e2754c
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Enable installation of openSUSE completion functions which are upstream
commit_time: 2012-02-07 15:58:03
expanded_srcmd5: e7a8e50c6e9eb5bbadd34f75dbcb8562
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: b466c94d21935ad71254e78ef7aa3b5e
mtime: 1324925887
name: osc.patch
size: 1523
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 5d5c8e88ce1631b3337a9a4444c009d9
mtime: 1325328500
name: zsh-4.3.12-fix-c02cond-test.patch
size: 812
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: ee16c2674687b8d861106d39ad80488c
mtime: 1328621263
name: zsh-enable-openSUSE-completion-functions.patch
size: 891
- md5: 067fa2bb6e20b1bb5b09d65a358384a6
mtime: 1328626475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21079
- md5: 7f3b3b8001df2167422481c742cb6571
mtime: 1328621263
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7699
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: e0147fc7631c1d01176b60ecfad686dd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: hmacht
number: 103060
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:hmacht:branches:shells
source_rev: '3'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 98.0
unexpanded_srcmd5: 6ae16cd5b8ba184538f39a00d6fba30e
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 38.0
commit_time: 2012-02-08 15:44:17
expanded_srcmd5: 86264b43645d14eb35d15de4b50057ca
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: b466c94d21935ad71254e78ef7aa3b5e
mtime: 1324925887
name: osc.patch
size: 1523
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 5d5c8e88ce1631b3337a9a4444c009d9
mtime: 1325328500
name: zsh-4.3.12-fix-c02cond-test.patch
size: 812
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: ee16c2674687b8d861106d39ad80488c
mtime: 1328621263
name: zsh-enable-openSUSE-completion-functions.patch
size: 891
- md5: 067fa2bb6e20b1bb5b09d65a358384a6
mtime: 1328626475
name: zsh.changes
size: 21079
- md5: 7f3b3b8001df2167422481c742cb6571
mtime: 1328621263
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7699
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: e0147fc7631c1d01176b60ecfad686dd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 98.038
unexpanded_srcmd5: 6ae16cd5b8ba184538f39a00d6fba30e
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2012-02-08 15:44:22
expanded_srcmd5: 7e5752b8a118083b866d0aa716248002
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: b466c94d21935ad71254e78ef7aa3b5e
mtime: 1324925887
name: osc.patch
size: 1523
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 5d5c8e88ce1631b3337a9a4444c009d9
mtime: 1325328500
name: zsh-4.3.12-fix-c02cond-test.patch
size: 812
- md5: 11766b0dd674a513810903cd33ffcac4
mtime: 1324373637
name: zsh-4.3.15.tar.bz2
size: 2969951
- md5: ee16c2674687b8d861106d39ad80488c
mtime: 1328621263
name: zsh-enable-openSUSE-completion-functions.patch
size: 891
- md5: 067fa2bb6e20b1bb5b09d65a358384a6
mtime: 1328626475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21079
- md5: 7f3b3b8001df2167422481c742cb6571
mtime: 1328621263
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7699
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: e0147fc7631c1d01176b60ecfad686dd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 103061
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '98'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 99.0
unexpanded_srcmd5: ab51ad55fb34926bcd04602ff010392c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 4.3.17\n * Contains fixes for possible speed regression\
\ introduced \n in 4.3.15 (new option HASH_EXECUTABLES_ONLY)\n * Improvements\
\ to (bash) completion and shell emulation mode \n- Drop all the patches, all\
\ upstream"
commit_time: 2012-02-27 10:15:24
expanded_srcmd5: a31c41bc45d3a3df1d3a8fb90b6d57da
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: ecb3c5985edec46b0bd0b20bae0f2e36
mtime: 1330334124
name: zsh.changes
size: 21435
- md5: bb19114a83e66b0cbdb6d40a2a7ff0a1
mtime: 1330334124
name: zsh.spec
size: 7519
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: ee45f866cddbb3ea4cc63c334698d923
package: zsh
project: shells
rev: 100.0
unexpanded_srcmd5: 29080c05aff806783cd01f7c73eb75fd
userid: namtrac
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 39.0
commit_time: 2012-02-27 18:39:10
expanded_srcmd5: feb84c125733a46d4e1ca574447252d1
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: ecb3c5985edec46b0bd0b20bae0f2e36
mtime: 1330334124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21435
- md5: bb19114a83e66b0cbdb6d40a2a7ff0a1
mtime: 1330334124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7519
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: ee45f866cddbb3ea4cc63c334698d923
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 100.039
unexpanded_srcmd5: 29080c05aff806783cd01f7c73eb75fd
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2012-02-27 18:39:15
expanded_srcmd5: da24d9f975e31f275970ce056a66bb47
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: ecb3c5985edec46b0bd0b20bae0f2e36
mtime: 1330334124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21435
- md5: bb19114a83e66b0cbdb6d40a2a7ff0a1
mtime: 1330334124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7519
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: ee45f866cddbb3ea4cc63c334698d923
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 107122
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '100'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 101.0
unexpanded_srcmd5: 2010f3f0d974a3bd59a201bd011c6327
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Don't need this workaround anymore
commit_time: 2012-04-17 14:01:38
expanded_srcmd5: 560c4937661b419c08483982466c80c0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: ecb3c5985edec46b0bd0b20bae0f2e36
mtime: 1330334124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21435
- md5: 5c061bd271a25db37aa1ca73dbef3ea1
mtime: 1334664098
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7437
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 9f849aac95ad07c00fe14ed95a736266
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 102.0
unexpanded_srcmd5: 2b1d7f9c6631c577c0bb97e75bab62d9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 40.0
commit_time: 2012-06-20 11:27:02
expanded_srcmd5: 560c4937661b419c08483982466c80c0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: ecb3c5985edec46b0bd0b20bae0f2e36
mtime: 1330334124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21435
- md5: 5c061bd271a25db37aa1ca73dbef3ea1
mtime: 1334664098
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7437
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: 9f849aac95ad07c00fe14ed95a736266
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 102.04
unexpanded_srcmd5: 2b1d7f9c6631c577c0bb97e75bab62d9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- buildrequire makeinfo to fix build'
commit_time: 2012-07-20 01:57:32
expanded_srcmd5: 449cf76a85f8628e9e291741b32ca368
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: 182a172cdfd776eb436fabe5b0b63b9c
mtime: 1342684709
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21588
- md5: c3ff5f718d335a37374717ad9197b16f
mtime: 1342684709
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7499
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: dbb8f6bc3df07371d63248770be979d4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: coolo
number: 128306
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:coolo:branches:openSUSE:Factory
source_rev: '2'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 103.0
unexpanded_srcmd5: 8b34f965c1b341f609f3d714cd4e6ea5
userid: prusnak
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 41.0
commit_time: 2012-07-20 10:26:00
expanded_srcmd5: b0da8e0d6b37edc4ef5e03bea8b99a53
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: 182a172cdfd776eb436fabe5b0b63b9c
mtime: 1342684709
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21588
- md5: c3ff5f718d335a37374717ad9197b16f
mtime: 1342684709
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7499
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: dbb8f6bc3df07371d63248770be979d4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 103.041
unexpanded_srcmd5: 8b34f965c1b341f609f3d714cd4e6ea5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2012-07-20 10:26:00
expanded_srcmd5: 177fcb9b8a304e51b1b1dca94ff014b1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: 182a172cdfd776eb436fabe5b0b63b9c
mtime: 1342684709
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21588
- md5: c3ff5f718d335a37374717ad9197b16f
mtime: 1342684709
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7499
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
files_hash: dbb8f6bc3df07371d63248770be979d4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: prusnak
number: 128439
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '103'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 104.0
unexpanded_srcmd5: 54d013963a03edc2434e36407582258a
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- we need tex2html too, which is provided by texinfo'
commit_time: 2012-07-22 21:22:47
expanded_srcmd5: de9a26b90d3c8a07762a3f4f4b071177
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
mtime: 1309365132
name: dotzshrc.rh
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: 64add6b356176ec8ff8df4f74433a607
mtime: 1342963271
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21757
- md5: 7988318584889ff0a74799db34b8814b
mtime: 1342963271
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7523
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 81244eb50c48321c4af80684ba684c1a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: coolo
number: 128654
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:coolo:branches:openSUSE:Factory
source_rev: '2'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 105.0
unexpanded_srcmd5: ccb92bcc6a81aca36a9c6acebff0962f
userid: elvigia
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 42.0
commit_time: 2012-07-23 10:49:16
expanded_srcmd5: b65fa865eba3baf17d9c62918b8e2ec9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: 64add6b356176ec8ff8df4f74433a607
mtime: 1342963271
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21757
- md5: 7988318584889ff0a74799db34b8814b
mtime: 1342963271
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7523
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 81244eb50c48321c4af80684ba684c1a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 105.042
unexpanded_srcmd5: ccb92bcc6a81aca36a9c6acebff0962f
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2012-07-23 10:49:17
expanded_srcmd5: 1d22cd8a8fc51ba4a554f6fb928ee17f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 8258967060b2654f30001a011946ac6a
mtime: 1330334124
name: zsh-4.3.17.tar.bz2
size: 2978903
- md5: 64add6b356176ec8ff8df4f74433a607
mtime: 1342963271
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21757
- md5: 7988318584889ff0a74799db34b8814b
mtime: 1342963271
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7523
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 81244eb50c48321c4af80684ba684c1a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: elvigia
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 128701
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: shells
source_rev: '105'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 106.0
unexpanded_srcmd5: 6a0c0e5eb7179c14e34c07f9056c42df
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Version update to 5.0.0\n * No real changes since 4.3.17"
commit_time: 2012-08-09 23:28:39
expanded_srcmd5: 0b5818e78c9cbf80a1a4013c0559db84
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8484468925cec8d9a84b8b04797e764
mtime: 1344547718
name: zsh-5.0.0.tar.bz2
size: 3014362
- md5: c35eda4b363fa64eadd3af3c0b7a717d
mtime: 1344547719
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21934
- md5: 02f5139fb20ac1950959bc399f083b5f
mtime: 1344547719
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7557
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 6e6ac8e856c2ae731d2230ef761138a4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 107.0
unexpanded_srcmd5: 9caa1565be3c0ea807c9d25f448febf9
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 43.0
commit_time: 2012-08-12 15:30:03
expanded_srcmd5: 5e3b07bfaecc6a0055b15753f2ef0c11
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8484468925cec8d9a84b8b04797e764
mtime: 1344547718
name: zsh-5.0.0.tar.bz2
size: 3014362
- md5: c35eda4b363fa64eadd3af3c0b7a717d
mtime: 1344547719
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21934
- md5: 02f5139fb20ac1950959bc399f083b5f
mtime: 1344547719
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7557
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7043
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 6e6ac8e856c2ae731d2230ef761138a4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 107.043
unexpanded_srcmd5: 9caa1565be3c0ea807c9d25f448febf9
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: baserev update by copy to link target
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2012-08-12 15:30:04
expanded_srcmd5: 8194572ea8c74f12d09ef8fc9f5b8e58
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8484468925cec8d9a84b8b04797e764
mtime: 1344547718
name: zsh-5.0.0.tar.bz2
size: 3014362
- md5: c35eda4b363fa64eadd3af3c0b7a717d
mtime: 1344547719
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 21934
- md5: 02f5139fb20ac1950959bc399f083b5f
mtime: 1344547719
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7557
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 6e6ac8e856c2ae731d2230ef761138a4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 130572
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '107'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 108.0
unexpanded_srcmd5: 2c6602c7e892f2900539c79d2fad6fe7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- buildrequire groff needed to build helpfiles'
commit_time: 2012-10-26 17:58:01
expanded_srcmd5: 9755a61ee1b2d2c0fd3fe63a718b5d25
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8484468925cec8d9a84b8b04797e764
mtime: 1344547718
name: zsh-5.0.0.tar.bz2
size: 3014362
- md5: a724f2ec3d6b1e582c113a4e58fadc6c
mtime: 1351263550
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22097
- md5: adfe942b8c83b4f09db5a2ae89db7bab
mtime: 1351263550
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7579
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 031af487ec2aecb3d9d49928e440efb3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: coolo
number: 139458
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:coolo:branches:openSUSE:Factory
source_rev: '2'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 109.0
unexpanded_srcmd5: aa0f5f5e505fb8407d6c4ffb7412ab87
userid: elvigia
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 44.0
commit_time: 2012-10-27 07:58:13
expanded_srcmd5: 742ca869f392e0ea8906d609571aedde
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8484468925cec8d9a84b8b04797e764
mtime: 1344547718
name: zsh-5.0.0.tar.bz2
size: 3014362
- md5: a724f2ec3d6b1e582c113a4e58fadc6c
mtime: 1351263550
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22097
- md5: adfe942b8c83b4f09db5a2ae89db7bab
mtime: 1351263550
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7579
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 031af487ec2aecb3d9d49928e440efb3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 109.044
unexpanded_srcmd5: aa0f5f5e505fb8407d6c4ffb7412ab87
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2012-10-27 07:58:14
expanded_srcmd5: 6ad9c9eaa2d21cc913a10de64a6c5800
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8484468925cec8d9a84b8b04797e764
mtime: 1344547718
name: zsh-5.0.0.tar.bz2
size: 3014362
- md5: a724f2ec3d6b1e582c113a4e58fadc6c
mtime: 1351263550
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22097
- md5: adfe942b8c83b4f09db5a2ae89db7bab
mtime: 1351263550
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7579
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 031af487ec2aecb3d9d49928e440efb3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: elvigia
number: 139476
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '109'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 110.0
unexpanded_srcmd5: 521ecce4e56bcc9ef9977d758484c64b
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Test suite runs flaky in qemu-arm, disable it for now.'
commit_time: 2012-11-16 09:16:12
expanded_srcmd5: b29dd5182cd32c6223d4f7bac9805659
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8484468925cec8d9a84b8b04797e764
mtime: 1344547718
name: zsh-5.0.0.tar.bz2
size: 3014362
- md5: b0e0712f6bec2e725fcf4772d1076827
mtime: 1353037796
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22281
- md5: 0d12279d9148a3282deafe7d485ffe20
mtime: 1353037796
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7618
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: d68dbde25cd77bb2bdcc2b0f1192cbfc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: elvigia
number: 141528
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:elvigia:branches:shells
source_rev: '2'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 111.0
unexpanded_srcmd5: 21e7e566b427175d5fa9709775b32826
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 45.0
commit_time: 2012-11-16 14:53:30
expanded_srcmd5: b1209db8ab1b2f7c7f1b5f48ce3755aa
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8484468925cec8d9a84b8b04797e764
mtime: 1344547718
name: zsh-5.0.0.tar.bz2
size: 3014362
- md5: b0e0712f6bec2e725fcf4772d1076827
mtime: 1353037796
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22281
- md5: 0d12279d9148a3282deafe7d485ffe20
mtime: 1353037796
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7618
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: d68dbde25cd77bb2bdcc2b0f1192cbfc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 111.045
unexpanded_srcmd5: 21e7e566b427175d5fa9709775b32826
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2012-11-16 14:53:31
expanded_srcmd5: a1d27ad43a327fc4e2c450cbeda8fd0a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8484468925cec8d9a84b8b04797e764
mtime: 1344547718
name: zsh-5.0.0.tar.bz2
size: 3014362
- md5: b0e0712f6bec2e725fcf4772d1076827
mtime: 1353037796
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22281
- md5: 0d12279d9148a3282deafe7d485ffe20
mtime: 1353037796
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7618
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: d68dbde25cd77bb2bdcc2b0f1192cbfc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 141535
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: shells
source_rev: '111'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 112.0
unexpanded_srcmd5: 0f0e7e73cf5af7e2f4b252a0bb305136
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.0.2\n * Numeric constants in mathematical contexts\
\ can contain\n underscores.\n * functions -T turns on tracing for specific\
\ functions.\n- See the included NEWS file for other changes."
commit_time: 2012-12-24 17:07:54
expanded_srcmd5: 73db1c55fcc8a59a26bd6e84528a5e73
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: c590c6fe96a83e3c19826a21c573a628
mtime: 1356365274
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22607
- md5: 160658f1a239bb03c0ff2a3711935eea
mtime: 1356365274
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7618
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 99784ec72be9d34fe3b9b5c8fc06adef
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 113.0
unexpanded_srcmd5: ede96c0980f2399ee18981b20bfcef26
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 46.0
commit_time: 2012-12-28 22:52:35
expanded_srcmd5: 4a666ee9431d03a8421b6967b9ed2d77
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: c590c6fe96a83e3c19826a21c573a628
mtime: 1356365274
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22607
- md5: 160658f1a239bb03c0ff2a3711935eea
mtime: 1356365274
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7618
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 99784ec72be9d34fe3b9b5c8fc06adef
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 113.046
unexpanded_srcmd5: ede96c0980f2399ee18981b20bfcef26
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2012-12-28 22:52:36
expanded_srcmd5: 73efbb48ac6e6ef0b321d65f76081a8b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: c590c6fe96a83e3c19826a21c573a628
mtime: 1356365274
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22607
- md5: 160658f1a239bb03c0ff2a3711935eea
mtime: 1356365274
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7618
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 99784ec72be9d34fe3b9b5c8fc06adef
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 146351
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: shells
source_rev: '113'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 114.0
unexpanded_srcmd5: 8a1ef6edf8cd0410b43d3f2616ca6dcf
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 47.0
commit_time: 2013-01-25 11:46:27
expanded_srcmd5: 73efbb48ac6e6ef0b321d65f76081a8b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: c590c6fe96a83e3c19826a21c573a628
mtime: 1356365274
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22607
- md5: 160658f1a239bb03c0ff2a3711935eea
mtime: 1356365274
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7618
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 99784ec72be9d34fe3b9b5c8fc06adef
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 114.047
unexpanded_srcmd5: 8a1ef6edf8cd0410b43d3f2616ca6dcf
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Fix zypper completion [bnc#752112]\n * zsh-zypper-completion.patch\n\
- Fix osc completion\n * zsh-osc-suseversion.patch"
commit_time: 2013-01-28 15:56:34
expanded_srcmd5: d987d711499e735ef2a533a9fe764b76
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 4a720655df5f9a4e06bb0b58d638e90d
mtime: 1359320185
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22866
- md5: c0262cdcaf8febecb926b2c541fc6bad
mtime: 1359320186
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7728
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 9b71c978b8160351ba287df4f4442ab3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: Dmitry_R
number: 150103
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:Dmitry_R:branches:shells
source_rev: '2'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 115.0
unexpanded_srcmd5: 4dda6660557d3d9f5d996710b72d1284
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 48.0
commit_time: 2013-01-29 06:49:17
expanded_srcmd5: a797c5b6e879bca92758c1115f58dc3c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 4a720655df5f9a4e06bb0b58d638e90d
mtime: 1359320185
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22866
- md5: c0262cdcaf8febecb926b2c541fc6bad
mtime: 1359320186
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7728
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 9b71c978b8160351ba287df4f4442ab3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 115.048
unexpanded_srcmd5: 4dda6660557d3d9f5d996710b72d1284
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2013-01-29 06:49:18
expanded_srcmd5: d8f1e5d1f3a4d26a4a3593ce7bdb123a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 4a720655df5f9a4e06bb0b58d638e90d
mtime: 1359320185
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 22866
- md5: c0262cdcaf8febecb926b2c541fc6bad
mtime: 1359320186
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7728
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: b2a454bf8f1954dc7204f00301de3d20
mtime: 1322130144
name: zshrc
size: 7043
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 9b71c978b8160351ba287df4f4442ab3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 150181
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '115'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 116.0
unexpanded_srcmd5: 4e10fd676d6cf244c45df53850d5f8fe
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Fix custom completion support via /etc/zsh_completion.d\n- Add trim-unneeded-completions.patch\
\ to remove unneeded completions\n when building for openSUSE"
commit_time: 2013-03-21 11:20:30
expanded_srcmd5: a4ca33c13910bae247bf15460a7d31d9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 2091b0e3067a5f26d58b984498bd89ae
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23140
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b24c178ed619c49c96c3f5a5d892d778
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c16224131ae6b5af341c8f3e76650219
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 117.0
unexpanded_srcmd5: 5fca1ef49112637ae084cd601e002b97
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 49.0
commit_time: 2013-03-22 09:22:17
expanded_srcmd5: b45bb9333ea5fba06548b71cd351f081
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 2091b0e3067a5f26d58b984498bd89ae
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23140
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b24c178ed619c49c96c3f5a5d892d778
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c16224131ae6b5af341c8f3e76650219
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 117.049
unexpanded_srcmd5: 5fca1ef49112637ae084cd601e002b97
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2013-03-22 09:22:18
expanded_srcmd5: d571af3e2ade6b092b6d28146b42ce66
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 2091b0e3067a5f26d58b984498bd89ae
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23140
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b24c178ed619c49c96c3f5a5d892d778
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c16224131ae6b5af341c8f3e76650219
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 160415
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '117'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 118.0
unexpanded_srcmd5: 43530b95929d198644895679fcb04a83
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Fix custom completion support via /etc/zsh_completion.d (bnc#811356)'
commit_time: 2013-03-25 13:03:02
expanded_srcmd5: 04ac018c0e09d482dbc52bea02a8e492
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 13191c1949a36561e5ff7bded0aefbc5
mtime: 1364212982
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23153
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b24c178ed619c49c96c3f5a5d892d778
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 0c85534f82c7d97056a5e9b9fae5561f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 119.0
unexpanded_srcmd5: 8d99a3f63c22778b4994fd1ad6b7fa09
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 50.0
commit_time: 2013-04-02 14:02:24
expanded_srcmd5: f0114be39b26f3ff1c83f645b5eededd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 13191c1949a36561e5ff7bded0aefbc5
mtime: 1364212982
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23153
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b24c178ed619c49c96c3f5a5d892d778
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 0c85534f82c7d97056a5e9b9fae5561f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 119.05
unexpanded_srcmd5: 8d99a3f63c22778b4994fd1ad6b7fa09
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2013-04-02 14:02:25
expanded_srcmd5: 52fb00d8b0dbd5447e12b82f8d8dd408
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 13191c1949a36561e5ff7bded0aefbc5
mtime: 1364212982
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23153
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b24c178ed619c49c96c3f5a5d892d778
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 0c85534f82c7d97056a5e9b9fae5561f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: factory-maintainer
number: 162040
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '119'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 120.0
unexpanded_srcmd5: a9ae46ca72c82a01391fc6f543e10e3b
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Don''t set globdots it might lead to unexpected problems (bnc#815556)'
commit_time: 2013-04-22 11:23:02
expanded_srcmd5: d1bf78123e1186acae9c390d04cbc007
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 90989bcb959ec1eedf45f0644b578dc1
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23343
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 3a35f5322f5d10a8a9baadcd26a00ede
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 121.0
unexpanded_srcmd5: 56fa989def4a712b72379b852dd5295a
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 51.0
commit_time: 2013-04-22 14:33:18
expanded_srcmd5: 9cec6785552de78138a3b52986350c6a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 90989bcb959ec1eedf45f0644b578dc1
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23343
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 3a35f5322f5d10a8a9baadcd26a00ede
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 121.051
unexpanded_srcmd5: 56fa989def4a712b72379b852dd5295a
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2013-04-22 14:33:19
expanded_srcmd5: ab1a22d6ddd46d718febe7faa326c37b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 90989bcb959ec1eedf45f0644b578dc1
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23343
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 3a35f5322f5d10a8a9baadcd26a00ede
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 172801
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: shells
source_rev: '121'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 122.0
unexpanded_srcmd5: 1d8376edbda57a26940c16a2939cc55e
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 52.0
commit_time: 2013-09-20 10:19:56
expanded_srcmd5: ab1a22d6ddd46d718febe7faa326c37b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b8f2ad691acf58b3252225746480dcad
mtime: 1356365273
name: zsh-5.0.2.tar.bz2
size: 3025767
- md5: 076c9d98ea67d04407e615b075115f6d
mtime: 1359217481
name: zsh-osc-suseversion.patch
size: 798
- md5: 446b20fa3c0d58f381b811a83004b27d
mtime: 1359320184
name: zsh-zypper-completion.patch
size: 1146
- md5: 90989bcb959ec1eedf45f0644b578dc1
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23343
- md5: e195159d3a12bb7252621003327cf87a
mtime: 1363861230
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7848
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 3a35f5322f5d10a8a9baadcd26a00ede
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 122.052
unexpanded_srcmd5: 1d8376edbda57a26940c16a2939cc55e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.0.4\n * Small bugfix release\n- Add zsh-pipefix.patch\
\ to import pipe fixes from zsh.git\n- Remove upstream patches\n * zsh-osc-suseversion.patch\n\
\ * zsh-zypper-completion.patch"
commit_time: 2013-12-25 13:35:38
expanded_srcmd5: e95d145603657b828fcd983249c91a8b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 9829fe8932c25740173a272e8959cf8c
mtime: 1387974935
name: zsh-5.0.4.tar.bz2
size: 3093541
- md5: 3df7a2ee980fef6584c80866b354c64b
mtime: 1387974936
name: zsh-pipefix.patch
size: 4982
- md5: 8187ab74fb60a442f2aad6ad4aaeeebf
mtime: 1387974936
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23658
- md5: b17085bdef79aa398d95d2827d24331e
mtime: 1387974937
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7617
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 6e9d70daeb1bbe8ca55faf042af89fab
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 123.0
unexpanded_srcmd5: 4d47ad9abc1d561e35ebae53b21b1fdc
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 53.0
commit_time: 2013-12-26 17:42:43
expanded_srcmd5: de468900ccac9fe0c7820cfa585b4d29
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 9829fe8932c25740173a272e8959cf8c
mtime: 1387974935
name: zsh-5.0.4.tar.bz2
size: 3093541
- md5: 3df7a2ee980fef6584c80866b354c64b
mtime: 1387974936
name: zsh-pipefix.patch
size: 4982
- md5: 8187ab74fb60a442f2aad6ad4aaeeebf
mtime: 1387974936
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23658
- md5: b17085bdef79aa398d95d2827d24331e
mtime: 1387974937
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7617
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 6e9d70daeb1bbe8ca55faf042af89fab
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 123.053
unexpanded_srcmd5: 4d47ad9abc1d561e35ebae53b21b1fdc
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: baserev update by copy to link target
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2013-12-26 17:42:44
expanded_srcmd5: 1b4ca44d407324fa8699b2597273f400
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 9829fe8932c25740173a272e8959cf8c
mtime: 1387974935
name: zsh-5.0.4.tar.bz2
size: 3093541
- md5: 3df7a2ee980fef6584c80866b354c64b
mtime: 1387974936
name: zsh-pipefix.patch
size: 4982
- md5: 8187ab74fb60a442f2aad6ad4aaeeebf
mtime: 1387974936
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23658
- md5: b17085bdef79aa398d95d2827d24331e
mtime: 1387974937
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7617
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 6e9d70daeb1bbe8ca55faf042af89fab
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 212246
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '123'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 124.0
unexpanded_srcmd5: 9035d67064df2863387848bd79c24148
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.0.5\n * Fixes a couple of regression in 5.0.4\n\
- Remove zsh-pipefix.patch, merged upstream"
commit_time: 2014-01-07 09:45:48
expanded_srcmd5: f1e2a004385b061ed04417629dd54bb8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: db249ac47a319c9f1d787ce9399c100c
mtime: 1389084347
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23888
- md5: 396d67b584bd94b235d56a2e2eb8a9cb
mtime: 1389084347
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: aaabe91b75c883ae7a9c7c5b425f1be9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 125.0
unexpanded_srcmd5: 356304e5c25c36e45a10e1ba48aa9740
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 54.0
commit_time: 2014-01-07 13:59:54
expanded_srcmd5: 73b0ce867dc489b4cc9eebbd3e0a4491
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: db249ac47a319c9f1d787ce9399c100c
mtime: 1389084347
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23888
- md5: 396d67b584bd94b235d56a2e2eb8a9cb
mtime: 1389084347
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: aaabe91b75c883ae7a9c7c5b425f1be9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 125.054
unexpanded_srcmd5: 356304e5c25c36e45a10e1ba48aa9740
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2014-01-07 13:59:54
expanded_srcmd5: be8a62341004b29c04b8e8b1b79781df
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: db249ac47a319c9f1d787ce9399c100c
mtime: 1389084347
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 23888
- md5: 396d67b584bd94b235d56a2e2eb8a9cb
mtime: 1389084347
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: aaabe91b75c883ae7a9c7c5b425f1be9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 212971
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '125'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 126.0
unexpanded_srcmd5: 9458e30842c3ae0beedbe0c8738aa5e4
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Add zsh-update-zypper-completion.patch to update zypper\n completions,\
\ patch by Holger Macht and Thomas Mitterfellner."
commit_time: 2014-01-16 10:52:00
expanded_srcmd5: c460ab5bf9496ef23c24bd5d4ba922fa
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: c1f3030f64aabc337391359b08a9fbe1
mtime: 1389865918
name: zsh-update-zypper-completion.patch
size: 4955
- md5: 7cb93087378c06bcc0f8fded1109f369
mtime: 1389865918
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24127
- md5: ccc468f3cd96471e5023892f034392ca
mtime: 1389865919
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7634
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 53a76d1b7a632ccca87afc9a4feb7da1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 127.0
unexpanded_srcmd5: bf90613f056c2940dcf71aae03288a8c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 55.0
commit_time: 2014-01-16 15:38:30
expanded_srcmd5: f8f027a10c6afaca1ea3e2ed3f8ec2ae
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: c1f3030f64aabc337391359b08a9fbe1
mtime: 1389865918
name: zsh-update-zypper-completion.patch
size: 4955
- md5: 7cb93087378c06bcc0f8fded1109f369
mtime: 1389865918
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24127
- md5: ccc468f3cd96471e5023892f034392ca
mtime: 1389865919
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7634
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 53a76d1b7a632ccca87afc9a4feb7da1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 127.055
unexpanded_srcmd5: bf90613f056c2940dcf71aae03288a8c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2014-01-16 15:38:30
expanded_srcmd5: d9bfb078413e1c605551f8fe5b3bb112
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: c1f3030f64aabc337391359b08a9fbe1
mtime: 1389865918
name: zsh-update-zypper-completion.patch
size: 4955
- md5: 7cb93087378c06bcc0f8fded1109f369
mtime: 1389865918
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24127
- md5: ccc468f3cd96471e5023892f034392ca
mtime: 1389865919
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7634
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 53a76d1b7a632ccca87afc9a4feb7da1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 214085
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '127'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 128.0
unexpanded_srcmd5: 0a6f49bbed73a91adc02b4daf3eb5495
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Update zsh-update-zypper-completion.patch to v0.3'
commit_time: 2014-01-17 10:42:38
expanded_srcmd5: e25d4bd22e06d490dba02e3b08dd7e3e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: 1698a635df56fc7b1479f583bfbc78f9
mtime: 1389951758
name: zsh-update-zypper-completion.patch
size: 7349
- md5: 30fdad3feaabf19c58228f3930e584c0
mtime: 1389951758
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24297
- md5: ccc468f3cd96471e5023892f034392ca
mtime: 1389865919
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7634
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 58970e8c8ee1504a2f1bdc254649b505
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 129.0
unexpanded_srcmd5: 527bc43555e6a9bab7d8085b52af959b
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 56.0
commit_time: 2014-01-17 13:18:37
expanded_srcmd5: 7961e1b7f206bdefcb480b63aff18b54
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: 1698a635df56fc7b1479f583bfbc78f9
mtime: 1389951758
name: zsh-update-zypper-completion.patch
size: 7349
- md5: 30fdad3feaabf19c58228f3930e584c0
mtime: 1389951758
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24297
- md5: ccc468f3cd96471e5023892f034392ca
mtime: 1389865919
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7634
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 58970e8c8ee1504a2f1bdc254649b505
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 129.056
unexpanded_srcmd5: 527bc43555e6a9bab7d8085b52af959b
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: baserev update by copy to link target
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2014-01-17 13:18:38
expanded_srcmd5: 23ff6e87ec2e6de6c200e5af85bc7d53
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: 1698a635df56fc7b1479f583bfbc78f9
mtime: 1389951758
name: zsh-update-zypper-completion.patch
size: 7349
- md5: 30fdad3feaabf19c58228f3930e584c0
mtime: 1389951758
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24297
- md5: ccc468f3cd96471e5023892f034392ca
mtime: 1389865919
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7634
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 58970e8c8ee1504a2f1bdc254649b505
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 214151
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '129'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 130.0
unexpanded_srcmd5: f25180582230c247c8c4d85d420c874c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Rename Completion/openSUSE/Command/_SuSEconfig to _SUSEconfig\n (bnc#888989\
\ fate#316521)"
commit_time: 2014-08-06 15:02:37
expanded_srcmd5: f663b94019a2c753042b5011c42ae7fc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: 1698a635df56fc7b1479f583bfbc78f9
mtime: 1389951758
name: zsh-update-zypper-completion.patch
size: 7349
- md5: c9c3a4bb3c8fa775e437a7e3a0e530d0
mtime: 1407330156
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24506
- md5: d8c1957c2f5f22b4c3755fcec2edc8c0
mtime: 1407330157
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7805
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7124
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c55596398820f508757a1fff16ac4395
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 131.0
unexpanded_srcmd5: 8764bb7a3608052d5dc5eb2f87c53a70
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 57.0
commit_time: 2014-08-07 08:07:33
expanded_srcmd5: ca0cec74eb2746448abac72aca3f0035
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: 1698a635df56fc7b1479f583bfbc78f9
mtime: 1389951758
name: zsh-update-zypper-completion.patch
size: 7349
- md5: c9c3a4bb3c8fa775e437a7e3a0e530d0
mtime: 1407330156
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24506
- md5: d8c1957c2f5f22b4c3755fcec2edc8c0
mtime: 1407330157
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7805
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c55596398820f508757a1fff16ac4395
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 131.057
unexpanded_srcmd5: 8764bb7a3608052d5dc5eb2f87c53a70
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2014-08-07 08:07:34
expanded_srcmd5: 98bf9eff42b4730c6a562e96563c85c2
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6156dc2f19b0a067bdbc0fb7f81e2017
mtime: 1389084347
name: zsh-5.0.5.tar.bz2
size: 3104375
- md5: 1698a635df56fc7b1479f583bfbc78f9
mtime: 1389951758
name: zsh-update-zypper-completion.patch
size: 7349
- md5: c9c3a4bb3c8fa775e437a7e3a0e530d0
mtime: 1407330156
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24506
- md5: d8c1957c2f5f22b4c3755fcec2edc8c0
mtime: 1407330157
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7805
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c55596398820f508757a1fff16ac4395
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 243775
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '131'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 132.0
unexpanded_srcmd5: 2e5b91d34e2c2438e29e7f8e884447e8
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.0.6\n * See included ChangeLog\n- Remove zsh-update-zypper-completion.patch,\
\ fixed upstream"
commit_time: 2014-08-28 21:23:29
expanded_srcmd5: cfb9637dd30fdd3ebb36694bdf19e415
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7150a6abc2aa1a79d81ed9a282594225
mtime: 1409253794
name: zsh-5.0.6.tar.bz2
size: 3174858
- md5: 11bea0ecc6068fb59c1f3c57bf571fed
mtime: 1409253799
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24737
- md5: 3632b6e3e20f84225b59b880043cd37b
mtime: 1409253804
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 8945ed679c7b8f6f4c1ca68425a1a361
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 133.0
unexpanded_srcmd5: f7c52c2af220843f5426c140e8ddca52
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 58.0
commit_time: 2014-08-29 11:18:02
expanded_srcmd5: cfb9637dd30fdd3ebb36694bdf19e415
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7150a6abc2aa1a79d81ed9a282594225
mtime: 1409253794
name: zsh-5.0.6.tar.bz2
size: 3174858
- md5: 11bea0ecc6068fb59c1f3c57bf571fed
mtime: 1409253799
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24737
- md5: 3632b6e3e20f84225b59b880043cd37b
mtime: 1409253804
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 8945ed679c7b8f6f4c1ca68425a1a361
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 133.058
unexpanded_srcmd5: f7c52c2af220843f5426c140e8ddca52
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 59.0
commit_time: 2014-08-31 09:58:42
expanded_srcmd5: d5dc188abf71144b47e4d6127f912b08
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7150a6abc2aa1a79d81ed9a282594225
mtime: 1409253794
name: zsh-5.0.6.tar.bz2
size: 3174858
- md5: 11bea0ecc6068fb59c1f3c57bf571fed
mtime: 1409253799
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24737
- md5: 3632b6e3e20f84225b59b880043cd37b
mtime: 1409253804
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
size: 7571
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 8945ed679c7b8f6f4c1ca68425a1a361
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 133.117
unexpanded_srcmd5: f7c52c2af220843f5426c140e8ddca52
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2014-08-31 09:58:42
expanded_srcmd5: 4f5fd0d2a96ec28d27ea97ea0df5666e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7150a6abc2aa1a79d81ed9a282594225
mtime: 1409253794
name: zsh-5.0.6.tar.bz2
size: 3174858
- md5: 11bea0ecc6068fb59c1f3c57bf571fed
mtime: 1409253799
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24737
- md5: 3632b6e3e20f84225b59b880043cd37b
mtime: 1409253804
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
size: 7571
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 8945ed679c7b8f6f4c1ca68425a1a361
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 246763
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '133'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 134.0
unexpanded_srcmd5: e053d5a9a71b32d1ce0a6df8934ae893
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Add zsh-fix-pcre-n.patch to fix pcre_match() -n option'
commit_time: 2014-09-07 22:11:03
expanded_srcmd5: fafb43f60d9982e698e5720fb72c3b78
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7150a6abc2aa1a79d81ed9a282594225
mtime: 1409253794
name: zsh-5.0.6.tar.bz2
size: 3174858
- md5: d71962d3be318f52490cb5e51bd1704a
mtime: 1410120662
name: zsh-fix-pcre-n.patch
size: 1323
- md5: 9665f91c4d58971709cc61903f3829ed
mtime: 1410120662
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24913
- md5: 9660338847959ec0914b5fd07741bf1c
mtime: 1410120662
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7669
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: b7e7f41de9c6c27cd754ee483db15485
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 135.0
unexpanded_srcmd5: e89eb56bee45d5e05e00897eb73eb625
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 60.0
commit_time: 2014-09-10 07:27:36
expanded_srcmd5: caa342c32e11a0e13454fa84ae810725
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7150a6abc2aa1a79d81ed9a282594225
mtime: 1409253794
name: zsh-5.0.6.tar.bz2
size: 3174858
- md5: d71962d3be318f52490cb5e51bd1704a
mtime: 1410120662
name: zsh-fix-pcre-n.patch
size: 1323
- md5: 9665f91c4d58971709cc61903f3829ed
mtime: 1410120662
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24913
- md5: 9660338847959ec0914b5fd07741bf1c
mtime: 1410120662
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7669
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: b7e7f41de9c6c27cd754ee483db15485
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 135.06
unexpanded_srcmd5: e89eb56bee45d5e05e00897eb73eb625
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: baserev update by copy to link target
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2014-09-10 07:27:37
expanded_srcmd5: 9d0b23758c135e671b5cec5f18290660
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7150a6abc2aa1a79d81ed9a282594225
mtime: 1409253794
name: zsh-5.0.6.tar.bz2
size: 3174858
- md5: d71962d3be318f52490cb5e51bd1704a
mtime: 1410120662
name: zsh-fix-pcre-n.patch
size: 1323
- md5: 9665f91c4d58971709cc61903f3829ed
mtime: 1410120662
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 24913
- md5: 9660338847959ec0914b5fd07741bf1c
mtime: 1410120662
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7669
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: b7e7f41de9c6c27cd754ee483db15485
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 247923
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '135'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 136.0
unexpanded_srcmd5: 8f2657139b642165b9c7b3196cd3097a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.0.7\n * Small bugfixes\n * Includes a security\
\ fix to disallow evaluation of the\n initial values of integer variables imported\
\ from the environment\n- Remove zsh-fix-pcre-n.patch, fixed upstream"
commit_time: 2014-10-09 10:27:29
expanded_srcmd5: f4ce3f808bc10bff3edb27405c5370eb
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: d71962d3be318f52490cb5e51bd1704a
mtime: 1410120662
name: zsh-fix-pcre-n.patch
size: 1323
- md5: ac1800b0d2ed2a73bd930bef1aa4a734
mtime: 1412843248
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25250
- md5: fd28c254e838e5330edd69f0dc0a1c90
mtime: 1412843249
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 4a497d4d359fc1e2171ca9f1130e25b6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 137.0
unexpanded_srcmd5: ad5978823835493c39c8ef248ab18f75
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '-'
commit_time: 2014-10-09 10:27:40
expanded_srcmd5: a43a6389ac7a2fd3e7e7b9e3bf34e4a7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: ac1800b0d2ed2a73bd930bef1aa4a734
mtime: 1412843248
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25250
- md5: fd28c254e838e5330edd69f0dc0a1c90
mtime: 1412843249
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 083238867e93473aa3db8264083cf984
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 138.0
unexpanded_srcmd5: 29e1524a2391112fa7be986ee06aa112
userid: namtrac
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 61.0
commit_time: 2014-10-11 19:24:56
expanded_srcmd5: c65b88305547ff75591da0006e56ee03
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: ac1800b0d2ed2a73bd930bef1aa4a734
mtime: 1412843248
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25250
- md5: fd28c254e838e5330edd69f0dc0a1c90
mtime: 1412843249
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 083238867e93473aa3db8264083cf984
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 138.061
unexpanded_srcmd5: 29e1524a2391112fa7be986ee06aa112
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: baserev update by copy to link target
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2014-10-11 19:24:56
expanded_srcmd5: e0ef37059fc3c71a7d2adf314932012d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: ac1800b0d2ed2a73bd930bef1aa4a734
mtime: 1412843248
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25250
- md5: fd28c254e838e5330edd69f0dc0a1c90
mtime: 1412843249
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
size: 7571
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 083238867e93473aa3db8264083cf984
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 254813
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '138'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 139.0
unexpanded_srcmd5: b8e95c346c1e08a026054ea6732fc3e8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Harden CFLAGS/LDFLAGS'
commit_time: 2015-01-14 11:02:14
expanded_srcmd5: 4d7f2cfcb5cf666e319a1201373ef529
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: 2315777b505818b9384dd63cb98a2eec
mtime: 1421229733
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25393
- md5: 995140977eae1f567e6642e19dfa1882
mtime: 1421229733
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7620
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 502ccf75f66255f5035d000449cd6056
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 140.0
unexpanded_srcmd5: 28c0833fcbfb0d5860b4b50eb0435628
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 62.0
commit_time: 2015-01-20 19:11:51
expanded_srcmd5: c0070141786f48353082eb045433a72c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: 2315777b505818b9384dd63cb98a2eec
mtime: 1421229733
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25393
- md5: 995140977eae1f567e6642e19dfa1882
mtime: 1421229733
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7620
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 502ccf75f66255f5035d000449cd6056
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 140.062
unexpanded_srcmd5: 28c0833fcbfb0d5860b4b50eb0435628
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2015-01-20 19:11:51
expanded_srcmd5: 94114d99eb4777b23cd5659cdadf3e5f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: 2315777b505818b9384dd63cb98a2eec
mtime: 1421229733
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25393
- md5: 995140977eae1f567e6642e19dfa1882
mtime: 1421229733
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7620
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 502ccf75f66255f5035d000449cd6056
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 281259
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '140'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 141.0
unexpanded_srcmd5: 44ad5581758609cb8ac9f34108873ca7
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Add back rpm completion file (bnc#900424)'
commit_time: 2015-01-28 18:53:51
expanded_srcmd5: c3458aa8bba71de8a92d35745ba95ebe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fa48f01c66839d1106d53a63fe63f17a
mtime: 1422467630
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25556
- md5: 285faaf320d1b1a0473491b97450e0ad
mtime: 1422467631
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7727
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: db7093ae63e5815fc7e3145229be54a1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 142.0
unexpanded_srcmd5: 79bb47b325579a490af41a0b51178728
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 63.0
commit_time: 2015-01-30 20:30:57
expanded_srcmd5: 66fe339ab023e69d830d8dd725195840
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fa48f01c66839d1106d53a63fe63f17a
mtime: 1422467630
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25556
- md5: 285faaf320d1b1a0473491b97450e0ad
mtime: 1422467631
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7727
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: db7093ae63e5815fc7e3145229be54a1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 142.063
unexpanded_srcmd5: 79bb47b325579a490af41a0b51178728
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: baserev update by copy to link target
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2015-01-30 20:30:57
expanded_srcmd5: 057159d30094922001ea75006b3aa445
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fa48f01c66839d1106d53a63fe63f17a
mtime: 1422467630
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25556
- md5: 285faaf320d1b1a0473491b97450e0ad
mtime: 1422467631
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7727
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: db7093ae63e5815fc7e3145229be54a1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 283223
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '142'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 143.0
unexpanded_srcmd5: b226460ce71b5eaa33fef74849e22d5e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Add zsh-texi2html-randomness.patch to prevent random changes\n in texi2html\
\ output (bnc#916186)"
commit_time: 2015-02-05 11:56:22
expanded_srcmd5: 13a7c8f2b9bc3a52e6106c3b584af9ab
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: f2f4836e0d5302a0317a8005477961e5
mtime: 1423133782
name: zsh-texi2html-randomness.patch
size: 496
- md5: ac284aa01eda82ff927ae9b76f285b79
mtime: 1423133782
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25772
- md5: 70cf1a1db9c121e17229b74253ffd30f
mtime: 1423133782
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7786
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 1530b23bc9d89e75777adf2befe292ff
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 144.0
unexpanded_srcmd5: 4323ab6f0f39617b1d8309e3b96335fe
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '-'
commit_time: 2015-02-05 12:33:27
expanded_srcmd5: b901a080ebf512abc6260d075ae80a58
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: fa48f01c66839d1106d53a63fe63f17a
mtime: 1422467630
name: zsh.changes
size: 25556
- md5: 285faaf320d1b1a0473491b97450e0ad
mtime: 1422467631
name: zsh.spec
size: 7727
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: db7093ae63e5815fc7e3145229be54a1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 145.0
unexpanded_srcmd5: b681f0825ba1a56a2156cc59105a1bf9
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- BuildRequire texi2html instead of texinfo: the packages have been\n\
\ split completely now."
commit_time: 2015-02-10 17:12:54
expanded_srcmd5: a24018e1a03415401b8cd40bec97c861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 394a47bfaf59878df6aeb96fc532d6a9
mtime: 1423556907
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25770
- md5: 321a2a622a197a4857cf0e4d2f7cf446
mtime: 1423556907
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7729
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 2fd40e4b8f5ab6888736c0ed2e7bfab8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: dimstar
number: 285043
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:dimstar:Factory
source_rev: '3'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 146.0
unexpanded_srcmd5: c6727760524d236b23ca75a8ff76759b
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 64.0
commit_time: 2015-02-16 15:02:26
expanded_srcmd5: b11f678d8b91fd3c615f65e981ae5f4d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: 394a47bfaf59878df6aeb96fc532d6a9
mtime: 1423556907
name: zsh.changes
size: 25770
- md5: 321a2a622a197a4857cf0e4d2f7cf446
mtime: 1423556907
name: zsh.spec
size: 7729
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 2fd40e4b8f5ab6888736c0ed2e7bfab8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 146.064
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
unexpanded_srcmd5: c6727760524d236b23ca75a8ff76759b
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: baserev update by copy to link target
commit_time: 2015-02-16 15:02:27
expanded_srcmd5: bae33ba087244741c9f9a935623fb5b5
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: 394a47bfaf59878df6aeb96fc532d6a9
mtime: 1423556907
name: zsh.changes
size: 25770
- md5: 321a2a622a197a4857cf0e4d2f7cf446
mtime: 1423556907
name: zsh.spec
size: 7729
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: cb0bf37f076087cdfd6171ab92c5466d
mtime: 1366622582
name: zshrc
size: 7124
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 2fd40e4b8f5ab6888736c0ed2e7bfab8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: namtrac
number: 285134
source_package: zsh
source_project: shells
source_rev: '146'
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 147.0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
unexpanded_srcmd5: 5d132dbe9718b21470d3fa4f4118d9da
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ''
commit_time: 2015-04-22 13:40:37
expanded_srcmd5: 5c11970a35d9aebdd7801f98f61deffa
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0ebe981224e759c6bba935e8663afb9b
mtime: 1429699576
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 25956
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 321a2a622a197a4857cf0e4d2f7cf446
mtime: 1423556907
name: zsh.spec
size: 7729
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 7bb8f67e6f0c63eb5d7f17dd82a03218
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: hennevogel
number: 298548
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:hennevogel:branches:shells
source_rev: bda911902e172f57e3017545c9468a9d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 148.0
unexpanded_srcmd5: 7f91eb3c54680a864bcd943a5c141fe4
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 65.0
commit_time: 2015-04-25 16:46:10
expanded_srcmd5: 23f48ef7ada009878e80b4ba9c25adf7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: 0ebe981224e759c6bba935e8663afb9b
mtime: 1429699576
name: zsh.changes
size: 25956
- md5: 321a2a622a197a4857cf0e4d2f7cf446
mtime: 1423556907
name: zsh.spec
size: 7729
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 7bb8f67e6f0c63eb5d7f17dd82a03218
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 148.065
unexpanded_srcmd5: 7f91eb3c54680a864bcd943a5c141fe4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2015-04-25 16:46:11
expanded_srcmd5: 30eb46fa4346b7916c7ce1dcd493f8d5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: 0ebe981224e759c6bba935e8663afb9b
mtime: 1429699576
name: zsh.changes
size: 25956
- md5: 321a2a622a197a4857cf0e4d2f7cf446
mtime: 1423556907
name: zsh.spec
size: 7729
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 7bb8f67e6f0c63eb5d7f17dd82a03218
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
number: 298564
source_package: zsh
source_project: shells
source_rev: '148'
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 149.0
unexpanded_srcmd5: 0742c86d977491e4ffc5fde71a93de89
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Add gcc5-fix.patch to fix signames.c generation with gcc5'
commit_time: 2015-04-29 10:34:05
expanded_srcmd5: a15e84db8c979f17a577c8f94c5d65c6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: fce6580dd4278ca92446d7ffcb627f38
mtime: 1430296444
name: gcc5-fix.patch
size: 468
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d237dcc7daf77a6e06357b58e0d73c78
mtime: 1430296444
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 26135
- md5: d9250720d999b09187ea810618154a3e
mtime: 1430296445
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7772
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c3afcf8779b4fe8d858355e9a41b44e9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 150.0
unexpanded_srcmd5: 78dbc99120d4760a3a83ff4cac24eec3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Fix openSUSE versions in osc completion\n * zsh-osc-completion.patch"
commit_time: 2015-05-03 15:25:23
expanded_srcmd5: 3a311ded0e1f5c72d8d77d791aaaee05
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: fce6580dd4278ca92446d7ffcb627f38
mtime: 1430296444
name: gcc5-fix.patch
size: 468
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: f3d3899d680e44767c56e35e88a71287
mtime: 1430638602
name: zsh.changes
size: 26329
- md5: 9324bf96b7525a93dbdb6dd4f6848d54
mtime: 1430638602
name: zsh.spec
size: 7914
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: a6657188268650bda75e1085939de5aa
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: Dmitry_R
number: 305143
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:Dmitry_R:branches:shells
source_rev: '2'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 151.0
unexpanded_srcmd5: 64f14d0940333ffc169d30feafdd0d04
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 66.0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
commit_time: 2015-05-10 10:53:51
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
expanded_srcmd5: 32d93c82a6d425d8b2c2849bb2c2be5a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: fce6580dd4278ca92446d7ffcb627f38
mtime: 1430296444
name: gcc5-fix.patch
size: 468
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: f3d3899d680e44767c56e35e88a71287
mtime: 1430638602
name: zsh.changes
size: 26329
- md5: 9324bf96b7525a93dbdb6dd4f6848d54
mtime: 1430638602
name: zsh.spec
size: 7914
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: a6657188268650bda75e1085939de5aa
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 151.066
unexpanded_srcmd5: 64f14d0940333ffc169d30feafdd0d04
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: baserev update by copy to link target
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2015-05-10 10:53:52
expanded_srcmd5: f3bb962abcf9a87899cd83cc637e79c0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fce6580dd4278ca92446d7ffcb627f38
mtime: 1430296444
name: gcc5-fix.patch
size: 468
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 1cd396ce17952de50b8a89980d617f0a
mtime: 1412843248
name: zsh-5.0.7.tar.bz2
size: 3181030
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: f3d3899d680e44767c56e35e88a71287
mtime: 1430638602
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 26329
- md5: 9324bf96b7525a93dbdb6dd4f6848d54
mtime: 1430638602
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7914
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: a6657188268650bda75e1085939de5aa
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 305205
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '151'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 152.0
unexpanded_srcmd5: 565759d162d4ee8bd40fc3031949da04
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Update to version 5.0.8
- Remove gcc5-fix.patch, fixed upstream.'
commit_time: 2015-05-31 21:26:04
expanded_srcmd5: f34221ec4f04a3e980153305e7e4af01
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: e6759e8dd7b714d624feffd0a73ba0fe
mtime: 1433100363
name: zsh-5.0.8.tar.bz2
size: 3250542
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b11714deba456b8a950c3e3967e1fb97
mtime: 1433100363
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 26514
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: cc2685c7c066a633ba41ee58cf5ff90f
mtime: 1433100364
name: zsh.spec
size: 7837
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 8f9af03be2b71836b68222b9992e10da
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 153.0
unexpanded_srcmd5: 912a26755563d19b6fc4d2b88f773c5e
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: " * Global aliases can be created for syntactic tokens such as command\n\
\ separators (\";\", \"&\", \"|\", \"&&\", \"||\"), redirection operators,\
\ etc.\n * There have been various further improvements to builtin handling\n\
\ with the POSIX_BUILTINS option (off by default) for compatibility with\n\
\ the POSIX standard.\n * 'whence -v' is now more informative, and 'whence\
\ -S' shows you\n how a full chain of symbolic links resolves to a command.\n\
\ * The 'p' parameter flag now allows an argument to be specified\n as a reference\
\ to a variable, e.g. ${(ps.$sep.)foo} to split $foo\n on a string given by\
\ $sep.\n * The option FORCE_FLOAT now forces variables, not just constants,\n\
\ to floating point in arithmetic expressions.\n * The type of an assignment\
\ in arithmetic expressions, e.g. the\n type seen by the variable res in $((\
\ res = a = b )), is now\n more logical and C-like.\n * The default binding\
\ of 'u' in vi command mode has changed to undo\n multiple changes when invoked\
\ repeatedly. '^R' is now bound to redo\n changes. To revert to toggling of\
\ the last edit use:\n bindkey -a u vi-undo-change\n * Compatibility with\
\ Vim has been improved for vi editing mode. Most\n notably, Vim style text\
\ objects are supported and the region can be\n manipulated with vi commands\
\ in the same manner as Vim's visual mode.\n * Elements of the watch variable\
\ may now be patterns.\n * The logic for retrying history locking has been improved."
commit_time: 2015-06-01 10:10:13
expanded_srcmd5: 03035c8a37e8beb9d9c9afc947551e53
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: e6759e8dd7b714d624feffd0a73ba0fe
mtime: 1433100363
name: zsh-5.0.8.tar.bz2
size: 3250542
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c83f49e1cc811e275cb96f5f5cb4ec88
mtime: 1433146212
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 27964
- md5: cc2685c7c066a633ba41ee58cf5ff90f
mtime: 1433100364
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7837
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 5b76c251cd4dedd67e6aaeab9ec16921
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 154.0
unexpanded_srcmd5: 5250935b758a86ee3a402b21e4ba245f
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 67.0
commit_time: 2015-06-03 08:23:27
expanded_srcmd5: 51c1b58045c3b5be4f8aaa7166a0e674
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: e6759e8dd7b714d624feffd0a73ba0fe
mtime: 1433100363
name: zsh-5.0.8.tar.bz2
size: 3250542
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c83f49e1cc811e275cb96f5f5cb4ec88
mtime: 1433146212
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 27964
- md5: cc2685c7c066a633ba41ee58cf5ff90f
mtime: 1433100364
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7837
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 5b76c251cd4dedd67e6aaeab9ec16921
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 154.067
unexpanded_srcmd5: 5250935b758a86ee3a402b21e4ba245f
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: baserev update by copy to link target
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2015-06-03 08:23:28
expanded_srcmd5: 0aec2f5714d139a32321f6ac927d8b2d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
- md5: e6759e8dd7b714d624feffd0a73ba0fe
mtime: 1433100363
name: zsh-5.0.8.tar.bz2
size: 3250542
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c83f49e1cc811e275cb96f5f5cb4ec88
mtime: 1433146212
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 27964
- md5: cc2685c7c066a633ba41ee58cf5ff90f
mtime: 1433100364
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7837
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: 5b76c251cd4dedd67e6aaeab9ec16921
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 309607
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '154'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 155.0
unexpanded_srcmd5: 8fc8f4355c5efffe4c8e5b700e9c1f3d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Add printf-regress.patch to fix a printf regression boo#934175'
commit_time: 2015-06-14 14:58:35
expanded_srcmd5: e822034f0427340fe50e1e18845f6c32
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 50e8e43fa9519084aed3fbd0ce48486e
mtime: 1434286715
name: printf-regress.patch
size: 1465
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
- md5: e6759e8dd7b714d624feffd0a73ba0fe
mtime: 1433100363
name: zsh-5.0.8.tar.bz2
size: 3250542
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 783892cf2e97d048f5c56f60127ace6a
mtime: 1434286715
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 28148
- md5: 974d43106fe62b4637df3a6c7f2e3f8b
mtime: 1434286715
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7886
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: 5e7f6dc2b19eea85a043428f0accc288
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 156.0
unexpanded_srcmd5: 5d562d2a9ad75ad105ee68f9795241ce
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 68.0
commit_time: 2015-07-05 17:57:05
expanded_srcmd5: a86bfbdbe8976fdad575a88e1788cb1b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 50e8e43fa9519084aed3fbd0ce48486e
mtime: 1434286715
name: printf-regress.patch
size: 1465
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e6759e8dd7b714d624feffd0a73ba0fe
mtime: 1433100363
name: zsh-5.0.8.tar.bz2
size: 3250542
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 783892cf2e97d048f5c56f60127ace6a
mtime: 1434286715
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 28148
- md5: 974d43106fe62b4637df3a6c7f2e3f8b
mtime: 1434286715
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
size: 7886
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 5e7f6dc2b19eea85a043428f0accc288
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 156.068
unexpanded_srcmd5: 5d562d2a9ad75ad105ee68f9795241ce
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2015-07-05 17:57:05
expanded_srcmd5: 903421f3aea5b184568f80e91d0cc8ed
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 50e8e43fa9519084aed3fbd0ce48486e
mtime: 1434286715
name: printf-regress.patch
size: 1465
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e6759e8dd7b714d624feffd0a73ba0fe
mtime: 1433100363
name: zsh-5.0.8.tar.bz2
size: 3250542
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 783892cf2e97d048f5c56f60127ace6a
mtime: 1434286715
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 28148
- md5: 974d43106fe62b4637df3a6c7f2e3f8b
mtime: 1434286715
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7886
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 5e7f6dc2b19eea85a043428f0accc288
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
request:
creator: factory-maintainer
number: 312924
source_package: zsh
source_project: shells
source_rev: '156'
state: accepted
type: submit
rev: 157.0
unexpanded_srcmd5: ed7b3bc6f40f36fa6103b03ed7d9eef2
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.1\n * The print builtin has new options -x and\
\ -X to expand tabs.\n * Several new command completions and numerous updates\
\ to others.\n * Options to \"fc\" to segregate internal and shared history.\n\
\ * All emulations including \"sh\" use multibyte by default; several\n repairs\
\ to multibyte handling.\n * ZLE supports \"bracketed paste\" mode to avoid interpreting\
\ pasted\n newlines as accept-line. Pastes can be highlighted for visibility\n\
\ and to make it more obvious whether accept-line has occurred.\n * Improved\
\ (though still not perfect) POSIX compatibility for getopts\n builtin when\
\ POSIX_BUILTINS is set.\n * New setopt APPEND_CREATE for POSIX-compatible NO_CLOBBER\
\ behavior.\n * Completion of date values now displays in a calendar format when\n\
\ the complist module is available. Controllable by zstyle.\n * New parameter\
\ UNDO_LIMIT_NO for more control over ZLE undo repeat.\n * Several repairs/improvements\
\ to the contributed narrow-to-region\n ZLE function.\n * Many changes to\
\ child-process and signal handling to eliminate race\n conditions and avoid\
\ deadlocks on descriptor and memory management.\n * New builtin sysopen in zsh/system\
\ module for detailed control of\n file descriptor modes. \n- Remove printf-regress.patch,\
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
\ upstream."
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2015-09-01 08:45:51
expanded_srcmd5: 94f369aeeed96dd6d1ae648302c0c7da
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 50e8e43fa9519084aed3fbd0ce48486e
mtime: 1434286715
name: printf-regress.patch
size: 1465
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
- md5: fbf736a6540873f4fb7bdaf70cafb1f0
mtime: 1441089950
name: zsh-5.1.tar.xz
size: 2785404
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2cfa163aff7fe345fe499d8e5fdf82d4
mtime: 1441089950
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 29548
- md5: f8fb40ff15f5e49c7e4c6cf67086fff2
mtime: 1441089951
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7834
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: f5a2f45d45efe08ca4bef5e2631695ba
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 158.0
unexpanded_srcmd5: ecb9277913ae73360f5ad9922b1145a7
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '-'
commit_time: 2015-09-01 08:50:50
expanded_srcmd5: 0b97d6ce92b6458b11694135488daf30
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fbf736a6540873f4fb7bdaf70cafb1f0
mtime: 1441089950
name: zsh-5.1.tar.xz
size: 2785404
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2cfa163aff7fe345fe499d8e5fdf82d4
mtime: 1441089950
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 29548
- md5: f8fb40ff15f5e49c7e4c6cf67086fff2
mtime: 1441089951
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7834
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: fd5dbc63c7a1184cbb5a7966e85f75d7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 159.0
unexpanded_srcmd5: 555e588a6219ad58f0dfe2ae73aaf44c
userid: namtrac
- broken: false
comment: '- Add read1char_signals.patch to fix workers/36373'
commit_time: 2015-09-01 21:00:44
expanded_srcmd5: ad47191c17f66903849b4dd55903e54b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7635c7a8fa92c8b4a5b2dfceaea18c4a
mtime: 1441134043
name: read1char_signals.patch
size: 807
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fbf736a6540873f4fb7bdaf70cafb1f0
mtime: 1441089950
name: zsh-5.1.tar.xz
size: 2785404
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: aa388d4e667870dce0a8ccfe331bf73f
mtime: 1441134044
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 29718
- md5: e87cd182b100cd1986675dea811f2482
mtime: 1441134044
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7886
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 73978081312a4c555d49ec66a716f31b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 160.0
unexpanded_srcmd5: d01d9497262fe97df31e004b93b99963
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 69.0
commit_time: 2015-09-03 17:59:47
expanded_srcmd5: b2c763935f7c562c491343468ff35739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7635c7a8fa92c8b4a5b2dfceaea18c4a
mtime: 1441134043
name: read1char_signals.patch
size: 807
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fbf736a6540873f4fb7bdaf70cafb1f0
mtime: 1441089950
name: zsh-5.1.tar.xz
size: 2785404
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: aa388d4e667870dce0a8ccfe331bf73f
mtime: 1441134044
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 29718
- md5: e87cd182b100cd1986675dea811f2482
mtime: 1441134044
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7886
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 73978081312a4c555d49ec66a716f31b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 160.069
unexpanded_srcmd5: d01d9497262fe97df31e004b93b99963
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2015-09-03 17:59:47
expanded_srcmd5: 405d9d59eb99b651f4f762b97f891557
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7635c7a8fa92c8b4a5b2dfceaea18c4a
mtime: 1441134043
name: read1char_signals.patch
size: 807
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fbf736a6540873f4fb7bdaf70cafb1f0
mtime: 1441089950
name: zsh-5.1.tar.xz
size: 2785404
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: aa388d4e667870dce0a8ccfe331bf73f
mtime: 1441134044
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 29718
- md5: e87cd182b100cd1986675dea811f2482
mtime: 1441134044
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7886
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 73978081312a4c555d49ec66a716f31b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 328399
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '160'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 161.0
unexpanded_srcmd5: 3f6cb635776627ba3ef7f05f60672365
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.1.1\n * Bug fixes for regressions in 5.1 release\n\
- Remove read1char_signals.patch, fixed upstream."
commit_time: 2015-09-12 09:51:55
expanded_srcmd5: 37b99bf706e30c5dc8cb8e2f039ee1ac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0e8ea3313300277a04cee80836507bae
mtime: 1442044314
name: zsh-5.1.1.tar.xz
size: 2788676
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b373c644fdb74d070e09016ba23ff0bf
mtime: 1442044314
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 29957
- md5: 8aa1991aa4061b24681f1f9db48769cd
mtime: 1442044314
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7836
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: fe0bc941e6a894a0522de986c48d31b7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 162.0
unexpanded_srcmd5: 27b9c84084c1451084477cd039710959
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 70.0
commit_time: 2015-09-17 09:18:28
expanded_srcmd5: 21c1651bfe66a4a86a56dc6b8b99845f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0e8ea3313300277a04cee80836507bae
mtime: 1442044314
name: zsh-5.1.1.tar.xz
size: 2788676
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b373c644fdb74d070e09016ba23ff0bf
mtime: 1442044314
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 29957
- md5: 8aa1991aa4061b24681f1f9db48769cd
mtime: 1442044314
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7836
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: fe0bc941e6a894a0522de986c48d31b7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 162.07
unexpanded_srcmd5: 27b9c84084c1451084477cd039710959
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2015-09-17 09:18:28
expanded_srcmd5: 8d47c896808691c2e465186878d059eb
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0e8ea3313300277a04cee80836507bae
mtime: 1442044314
name: zsh-5.1.1.tar.xz
size: 2788676
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b373c644fdb74d070e09016ba23ff0bf
mtime: 1442044314
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 29957
- md5: 8aa1991aa4061b24681f1f9db48769cd
mtime: 1442044314
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7836
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: fe0bc941e6a894a0522de986c48d31b7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 330592
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: shells
source_rev: '162'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 163.0
unexpanded_srcmd5: a869b3dd2fd2b9b495dfc03997ec42ca
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Remove -Wl,-z,now it breaks module loading rh#1277996'
commit_time: 2015-11-05 16:56:22
expanded_srcmd5: 741cfce0b8bc496e4ea3892bc90ba459
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0e8ea3313300277a04cee80836507bae
mtime: 1442044314
name: zsh-5.1.1.tar.xz
size: 2788676
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bf2ecdb63a1d8b7aa8300916e05e6cea
mtime: 1446738981
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 30132
- md5: 4ec0662ba4b45c2883d457e4a6501571
mtime: 1446738982
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7830
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: bd3d3b4790c024d6e9df6f1c605035cf
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 164.0
unexpanded_srcmd5: 31de2ddb62b63bb4f27b95498d51d067
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 71.0
commit_time: 2015-11-08 14:35:23
expanded_srcmd5: 24116ddc6dbaf2d1e94ba98515e6eef9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
name: zprofile.rhs
size: 168
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0e8ea3313300277a04cee80836507bae
mtime: 1442044314
name: zsh-5.1.1.tar.xz
size: 2788676
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bf2ecdb63a1d8b7aa8300916e05e6cea
mtime: 1446738981
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 30132
- md5: 4ec0662ba4b45c2883d457e4a6501571
mtime: 1446738982
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7830
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
name: zshrc.rhs
size: 640
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: bd3d3b4790c024d6e9df6f1c605035cf
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 164.071
unexpanded_srcmd5: 31de2ddb62b63bb4f27b95498d51d067
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2015-11-08 14:35:24
expanded_srcmd5: 8ce29ebd94800cf0af95f013af92e15c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
- md5: 0e8ea3313300277a04cee80836507bae
mtime: 1442044314
name: zsh-5.1.1.tar.xz
size: 2788676
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bf2ecdb63a1d8b7aa8300916e05e6cea
mtime: 1446738981
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 30132
- md5: 4ec0662ba4b45c2883d457e4a6501571
mtime: 1446738982
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7830
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: bd3d3b4790c024d6e9df6f1c605035cf
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 342578
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: shells
source_rev: '164'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 165.0
unexpanded_srcmd5: 8fa919091f6ee70ebb68a63aa76d9ed2
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.2\n * The new module zsh/param/private can be loaded\
\ to allow the shell\n to define parameters that are private to a function\
\ scope (i.e. are\n not propagated to nested functions called within this function).\n\
\ * The GLOB_STAR_SHORT option allows the pattern **/* to be shortened to\n \
\ just ** if no / follows. so **.c searches recursively for a file whose\n \
\ name has the suffix \".c\".\n * The effect of the WARN_CREATE_GLOBAL option\
\ has been significantly\n extended, so expect it to cause additional warning\
\ messages about\n parameters created globally within function scope."
commit_time: 2015-12-03 09:49:34
expanded_srcmd5: d28aaf492a5bf107f8b4b5f319fead47
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 514ca876eeda0637438f6a625acc9f7b
mtime: 1449132574
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 30860
- md5: 0ac4793bf97921d9251b7ecb95bbe6e6
mtime: 1449132574
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7828
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: cb9a89c02eebb560cbaf94bc8a6237cc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 166.0
unexpanded_srcmd5: 79ea8002452904836e3c1200ee0af575
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 72.0
commit_time: 2015-12-09 19:32:40
expanded_srcmd5: ef510f7646751463ece459e651ca1272
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 514ca876eeda0637438f6a625acc9f7b
mtime: 1449132574
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 30860
- md5: 0ac4793bf97921d9251b7ecb95bbe6e6
mtime: 1449132574
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7828
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: cb9a89c02eebb560cbaf94bc8a6237cc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 166.072
unexpanded_srcmd5: 79ea8002452904836e3c1200ee0af575
userid: buildservice-autocommit
- broken: false
comment: baserev update by copy to link target
commit_time: 2015-12-09 19:32:41
expanded_srcmd5: 0d780d15b44a4a397be4a0916f98be39
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 514ca876eeda0637438f6a625acc9f7b
mtime: 1449132574
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 30860
- md5: 0ac4793bf97921d9251b7ecb95bbe6e6
mtime: 1449132574
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7828
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: cb9a89c02eebb560cbaf94bc8a6237cc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 347277
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: shells
source_rev: '166'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 167.0
unexpanded_srcmd5: fcb6a20062aaf34325077e975463c5ce
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Add gpg signature'
commit_time: 2015-12-10 11:29:15
expanded_srcmd5: 9c9808c197dbd863e5e90be6b1c48c12
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 630efb1373c1c13886e634a3e43eb408
mtime: 1449741347
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 30999
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 544cdb737350efa356e01c9b5c83cd35
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7925
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: b825c459249c9249366621fc1e12c26d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: pluskalm
number: 348212
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:pluskalm:branches:shells
source_rev: '4'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 168.0
unexpanded_srcmd5: b7d9441ab3adf1fb2b6225f242211dcd
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 73.0
commit_time: 2015-12-17 15:53:50
expanded_srcmd5: 86afc8e1b10df7062122ee1eb9c1e99c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 630efb1373c1c13886e634a3e43eb408
mtime: 1449741347
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 30999
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 544cdb737350efa356e01c9b5c83cd35
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7925
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: b825c459249c9249366621fc1e12c26d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 168.073
unexpanded_srcmd5: b7d9441ab3adf1fb2b6225f242211dcd
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: baserev update by copy to link target
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2015-12-17 15:53:51
expanded_srcmd5: 18bf2f950b072516abbbda245fad93e9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
- md5: c0f422a7e88f3946800db8828cfa14c1
mtime: 1309349172
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 168
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 630efb1373c1c13886e634a3e43eb408
mtime: 1449741347
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 30999
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 544cdb737350efa356e01c9b5c83cd35
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7925
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: ea61df7da782ae900f18219735aa7e92
mtime: 1309349174
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 640
files_hash: b825c459249c9249366621fc1e12c26d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 348221
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '168'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 169.0
unexpanded_srcmd5: 08ed2fac0aef292525a48a9693531378
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Add CentOS [67] support
commit_time: 2016-05-25 14:25:38
expanded_srcmd5: 2430f4396852a291fa3462ccf612c3a0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 630efb1373c1c13886e634a3e43eb408
mtime: 1449741347
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 30999
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ae01b84db82eafd09f94896a78e3e750
mtime: 1464141876
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8282
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: f029bcbd56c5e6bd3a90ebbcbb5d29c3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: llua
number: 397822
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:llua:branches:shells
source_rev: 831a776e805f6d83085e22e48223005d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 170.0
unexpanded_srcmd5: 03aab92be1da61a2151a722bf2f677ef
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Add CentOS [67] support'
commit_time: 2016-05-25 14:30:55
expanded_srcmd5: 5486dd90f08a3502258edc87582fb9e1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0858cb2acc70799dbeb6cfd749fae8f6
mtime: 1464179454
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 31139
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ae01b84db82eafd09f94896a78e3e750
mtime: 1464141876
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8282
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c689695a5eb0e7f87e21912ee21790cb
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 171.0
unexpanded_srcmd5: 65635462f0335fe43cc0057ef553640f
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 74.0
commit_time: 2016-06-05 14:19:58
expanded_srcmd5: 0e5afcd229dc3e9df841331d3a819927
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
name: zprofile
size: 199
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 0858cb2acc70799dbeb6cfd749fae8f6
mtime: 1464179454
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 31139
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
- md5: ae01b84db82eafd09f94896a78e3e750
mtime: 1464141876
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8282
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: c689695a5eb0e7f87e21912ee21790cb
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 171.074
unexpanded_srcmd5: 65635462f0335fe43cc0057ef553640f
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2016-06-05 14:19:59
expanded_srcmd5: 19f9407afbe900973eace72da647fabd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d2b4b4f8eea848be68b1b9423f7fd07
mtime: 1196723013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 199
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0858cb2acc70799dbeb6cfd749fae8f6
mtime: 1464179454
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 31139
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ae01b84db82eafd09f94896a78e3e750
mtime: 1464141876
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8282
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 496dcf7d01bd6389ccaf289a45ea5698
mtime: 1309349174
name: zshprompt.pl
size: 6330
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c689695a5eb0e7f87e21912ee21790cb
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: factory-maintainer
number: 399482
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '171'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 172.0
unexpanded_srcmd5: 808cfb3a1155f3589a7502deadb2423f
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: clean up system-wide configuration
commit_time: 2016-08-31 11:49:40
expanded_srcmd5: 897299c52f9861756562c8538943d13f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bd92b62261b623aab9a7818a9e447577
mtime: 1467385699
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 109
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b6dfdc650f23b39d4f925fe492e7f422
mtime: 1472566992
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 31429
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 9d36aa82b521f7cc8eb3f0f02e464bf3
mtime: 1467386605
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8005
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 4bd7916fbf341f02fa9fc2e0ac3f06b9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: mmanno
number: 423857
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:mmanno:branches:shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_rev: '2'
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 173.0
unexpanded_srcmd5: 21a4f6dd3fd6fbbd32ec73e9b6c4f5e4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 75.0
commit_time: 2016-09-05 21:13:52
expanded_srcmd5: 7d78f9da1293c92129dafe5134e6fe9f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bd92b62261b623aab9a7818a9e447577
mtime: 1467385699
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 109
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b6dfdc650f23b39d4f925fe492e7f422
mtime: 1472566992
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 31429
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 9d36aa82b521f7cc8eb3f0f02e464bf3
mtime: 1467386605
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8005
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 4bd7916fbf341f02fa9fc2e0ac3f06b9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 173.075
unexpanded_srcmd5: 21a4f6dd3fd6fbbd32ec73e9b6c4f5e4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2016-09-05 21:13:53
expanded_srcmd5: 7a62707407982f935b344becb1f6fdc0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bd92b62261b623aab9a7818a9e447577
mtime: 1467385699
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 109
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b6dfdc650f23b39d4f925fe492e7f422
mtime: 1472566992
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 31429
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 9d36aa82b521f7cc8eb3f0f02e464bf3
mtime: 1467386605
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8005
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 4bd7916fbf341f02fa9fc2e0ac3f06b9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 423967
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '173'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 174.0
unexpanded_srcmd5: 3ac844230ef094df68d77267baf79c15
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Read /etc/profile as zsh again.'
commit_time: 2016-09-08 15:25:44
expanded_srcmd5: 72d1b4a9698e8f7b6373cbd23d6bc24a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ae98396f495b7b6aefc7dac0b894753e
mtime: 1473341143
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 93
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0e413add5169d47bd51331792d0e3b89
mtime: 1473341143
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 31582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 9d36aa82b521f7cc8eb3f0f02e464bf3
mtime: 1467386605
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8005
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 9a2d3412a736d0bbd2c0d7a0b4b8b518
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 175.0
unexpanded_srcmd5: 4d372839079778dad4cda6345562cf01
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 76.0
commit_time: 2016-09-08 18:05:51
expanded_srcmd5: f4e0c861f6473bdc9c5c1987bfb3a0ff
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ae98396f495b7b6aefc7dac0b894753e
mtime: 1473341143
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 93
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0e413add5169d47bd51331792d0e3b89
mtime: 1473341143
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 31582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 9d36aa82b521f7cc8eb3f0f02e464bf3
mtime: 1467386605
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8005
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 9a2d3412a736d0bbd2c0d7a0b4b8b518
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 175.076
unexpanded_srcmd5: 4d372839079778dad4cda6345562cf01
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2016-09-08 18:05:51
expanded_srcmd5: a2c91042552489e6593302bb8f8458d4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ae98396f495b7b6aefc7dac0b894753e
mtime: 1473341143
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 93
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: afe96fde08b70e23c1cab1ca7a68fb34
mtime: 1449132573
name: zsh-5.2.tar.xz
size: 2820108
- md5: f5e96fe7ab62ebc45a692fb54ca2e84d
mtime: 1449699864
name: zsh-5.2.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0e413add5169d47bd51331792d0e3b89
mtime: 1473341143
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 31582
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 9d36aa82b521f7cc8eb3f0f02e464bf3
mtime: 1467386605
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8005
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 9a2d3412a736d0bbd2c0d7a0b4b8b518
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 425719
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '175'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 176.0
unexpanded_srcmd5: a45b2f155bebc8f7adaed0fed5cbe1a1
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to zsh 5.3\n * Unicode9 support, this needs support from your\
\ terminal to\n work correctly.\n * The new word modifier ':P' computes the\
\ physical path of the\n argument.\n * The output of \"typeset -p\" uses \"\
export\" commands or the \"-g\"\n option for parameters that are not local\
\ to the current scope.\n * vi-repeat-change can repeat user-defined widgets\
\ if the widget\n calls zle -f vichange.\n * The parameter $registers now\
\ makes the contents of vi register\n buffers available to user-defined widgets.\n\
\ * New vi-up-case and vi-down-case builtin widgets bound to gU/gu\n (or U/u\
\ in visual mode) for doing case conversion.\n * A new select-word-match function\
\ provides vim-style text objects\n with configurable word boundaries using\
\ the existing\n match-words-by-style mechanism.\n * Support for the conditional\
\ expression [[ -v var ]] to test if a\n variable is set for compatibility\
\ with other shells.\n * The print and printf builtins have a new option -v to\
\ assign the\n output to a variable.\n * New x: syntax in completion match\
\ specifications make it possible\n to disable match specifications hardcoded\
\ in completion functions.\n- Re-add custom zshrc and zshenv to unbreak compatibility\
\ with old\n usage (boo#998858)."
commit_time: 2016-12-14 11:01:58
expanded_srcmd5: cc29c33802b844443e1cfd35be576d86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 70d75ef84294c274243d2b35b184ae60
mtime: 1481709716
name: fix-printf.patch
size: 842
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c5ba34e68fcf62a2e78adc56bf3d328a
mtime: 1481709717
name: zsh-5.3.tar.xz
size: 2928684
- md5: 9b38eec96ec1a6b579b3486087f39a33
mtime: 1481709717
name: zsh-5.3.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bf6db32cc585e8cada810f8540a6d055
mtime: 1481709717
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 32958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 09d6e402123636148e4a39fdd9d46c67
mtime: 1481709717
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8221
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 8f902377213b4000760582036eae06a1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 177.0
unexpanded_srcmd5: ae85794c34eb00eed67b1b4095a0d7c0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '-'
commit_time: 2016-12-14 11:06:51
expanded_srcmd5: d2dadbea367cb2ef5e050093db0b1cf5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 70d75ef84294c274243d2b35b184ae60
mtime: 1481709716
name: fix-printf.patch
size: 842
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c5ba34e68fcf62a2e78adc56bf3d328a
mtime: 1481709717
name: zsh-5.3.tar.xz
size: 2928684
- md5: 9b38eec96ec1a6b579b3486087f39a33
mtime: 1481709717
name: zsh-5.3.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 029877695a09eeffe8398e7cec633c09
mtime: 1481710011
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 33012
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 09d6e402123636148e4a39fdd9d46c67
mtime: 1481709717
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8221
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 3af848ae1f0ef13dc66ced7fdbee1b9e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 178.0
unexpanded_srcmd5: b88804aaa0f377ba283a732007bfdc6c
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 77.0
commit_time: 2016-12-16 11:59:34
expanded_srcmd5: db91421f5c516b508c73fb8b3fac9bfc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 70d75ef84294c274243d2b35b184ae60
mtime: 1481709716
name: fix-printf.patch
size: 842
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c5ba34e68fcf62a2e78adc56bf3d328a
mtime: 1481709717
name: zsh-5.3.tar.xz
size: 2928684
- md5: 9b38eec96ec1a6b579b3486087f39a33
mtime: 1481709717
name: zsh-5.3.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 029877695a09eeffe8398e7cec633c09
mtime: 1481710011
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 33012
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 09d6e402123636148e4a39fdd9d46c67
mtime: 1481709717
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8221
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
files_hash: 3af848ae1f0ef13dc66ced7fdbee1b9e
package: zsh
project: shells
rev: 178.077
unexpanded_srcmd5: b88804aaa0f377ba283a732007bfdc6c
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2016-12-16 11:59:34
expanded_srcmd5: 41bb60cac25807d56a11a330aa9c65d2
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 70d75ef84294c274243d2b35b184ae60
mtime: 1481709716
name: fix-printf.patch
size: 842
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c5ba34e68fcf62a2e78adc56bf3d328a
mtime: 1481709717
name: zsh-5.3.tar.xz
size: 2928684
- md5: 9b38eec96ec1a6b579b3486087f39a33
mtime: 1481709717
name: zsh-5.3.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 029877695a09eeffe8398e7cec633c09
mtime: 1481710011
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 33012
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 09d6e402123636148e4a39fdd9d46c67
mtime: 1481709717
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8221
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 3af848ae1f0ef13dc66ced7fdbee1b9e
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 445732
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: shells
source_rev: '178'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 179.0
unexpanded_srcmd5: 3ae5eccd94e35e54c28d7a28775deb39
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- fix broken completion for filterdiff: fix-patchutils-completion.patch\n\
\ (boo#1019130)"
commit_time: 2017-02-06 14:53:32
expanded_srcmd5: d9a029431116c6ccc22ef577a7fc9089
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8ce1dd8955386daf1606d3c33283e1b
mtime: 1484066059
name: fix-patchutils-completion.patch
size: 1269
- md5: 70d75ef84294c274243d2b35b184ae60
mtime: 1481709716
name: fix-printf.patch
size: 842
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c5ba34e68fcf62a2e78adc56bf3d328a
mtime: 1481709717
name: zsh-5.3.tar.xz
size: 2928684
- md5: 9b38eec96ec1a6b579b3486087f39a33
mtime: 1481709717
name: zsh-5.3.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 440839cf8b232d05669ab7ae20c604cf
mtime: 1484066060
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 33219
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 62bfb6a9a38bda5db737ebae0b952a6e
mtime: 1484066060
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8281
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 427ac21acbe4fc61ed51fa69586cf3ea
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: matejcik
number: 449562
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:matejcik:branches:shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_rev: '2'
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 180.0
unexpanded_srcmd5: a63610e0c5e1eb009758decc0d0d9dbe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 78.0
commit_time: 2017-02-11 01:30:57
expanded_srcmd5: 1d84db11d20d883ac0fc269e5e84f366
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8ce1dd8955386daf1606d3c33283e1b
mtime: 1484066059
name: fix-patchutils-completion.patch
size: 1269
- md5: 70d75ef84294c274243d2b35b184ae60
mtime: 1481709716
name: fix-printf.patch
size: 842
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c5ba34e68fcf62a2e78adc56bf3d328a
mtime: 1481709717
name: zsh-5.3.tar.xz
size: 2928684
- md5: 9b38eec96ec1a6b579b3486087f39a33
mtime: 1481709717
name: zsh-5.3.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 440839cf8b232d05669ab7ae20c604cf
mtime: 1484066060
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 33219
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 62bfb6a9a38bda5db737ebae0b952a6e
mtime: 1484066060
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8281
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 427ac21acbe4fc61ed51fa69586cf3ea
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 180.078
unexpanded_srcmd5: a63610e0c5e1eb009758decc0d0d9dbe
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2017-02-11 01:30:57
expanded_srcmd5: e2344f385f0ce65810e3fe9cad17889b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8ce1dd8955386daf1606d3c33283e1b
mtime: 1484066059
name: fix-patchutils-completion.patch
size: 1269
- md5: 70d75ef84294c274243d2b35b184ae60
mtime: 1481709716
name: fix-printf.patch
size: 842
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c5ba34e68fcf62a2e78adc56bf3d328a
mtime: 1481709717
name: zsh-5.3.tar.xz
size: 2928684
- md5: 9b38eec96ec1a6b579b3486087f39a33
mtime: 1481709717
name: zsh-5.3.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 440839cf8b232d05669ab7ae20c604cf
mtime: 1484066060
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 33219
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 62bfb6a9a38bda5db737ebae0b952a6e
mtime: 1484066060
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8281
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 427ac21acbe4fc61ed51fa69586cf3ea
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 455002
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '180'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 181.0
unexpanded_srcmd5: a7478fba54bf5f783a14043d2fd2eb8d
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Update that fixes at least some annoying completion bugs and the printf
bug (patched on openSUSE) is also resolved.
commit_time: 2017-03-05 20:32:31
expanded_srcmd5: 7444a8051c41f83e70a08f959414c1e2
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8ce1dd8955386daf1606d3c33283e1b
mtime: 1484066059
name: fix-patchutils-completion.patch
size: 1269
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 67d3e5ed99de68340c16aef613b0ecf7
mtime: 1488724478
name: zsh-5.3.1.tar.xz
size: 2928832
- md5: a0b1584fddb060b6696482f5f5e8b2c8
mtime: 1488724478
name: zsh-5.3.1.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fbf2c668a30d9d92b4663d594adc8006
mtime: 1488725930
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 33571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ef95dd047dd456b17b96f56ac8d8d1ae
mtime: 1488724895
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8201
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 585cb13a8765112b9e6e4a29bc97ebf2
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: susnux
number: 477019
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:susnux:branches:shells
source_rev: '4'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 182.0
unexpanded_srcmd5: 3edbd9cb1e7405712828aaa59a552df6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 79.0
commit_time: 2017-03-10 20:44:29
expanded_srcmd5: 45a275e4046c3a8b3366995b9dd9166b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8ce1dd8955386daf1606d3c33283e1b
mtime: 1484066059
name: fix-patchutils-completion.patch
size: 1269
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 67d3e5ed99de68340c16aef613b0ecf7
mtime: 1488724478
name: zsh-5.3.1.tar.xz
size: 2928832
- md5: a0b1584fddb060b6696482f5f5e8b2c8
mtime: 1488724478
name: zsh-5.3.1.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fbf2c668a30d9d92b4663d594adc8006
mtime: 1488725930
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 33571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ef95dd047dd456b17b96f56ac8d8d1ae
mtime: 1488724895
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8201
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 585cb13a8765112b9e6e4a29bc97ebf2
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 182.079
unexpanded_srcmd5: 3edbd9cb1e7405712828aaa59a552df6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2017-03-10 20:44:29
expanded_srcmd5: d64b2b5b5f9c8b550c00b730d039d746
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e8ce1dd8955386daf1606d3c33283e1b
mtime: 1484066059
name: fix-patchutils-completion.patch
size: 1269
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 67d3e5ed99de68340c16aef613b0ecf7
mtime: 1488724478
name: zsh-5.3.1.tar.xz
size: 2928832
- md5: a0b1584fddb060b6696482f5f5e8b2c8
mtime: 1488724478
name: zsh-5.3.1.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 473
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fbf2c668a30d9d92b4663d594adc8006
mtime: 1488725930
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 33571
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
name: zsh.keyring
size: 1718
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ef95dd047dd456b17b96f56ac8d8d1ae
mtime: 1488724895
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8201
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 585cb13a8765112b9e6e4a29bc97ebf2
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 477054
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '182'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 183.0
unexpanded_srcmd5: 9ee1834e194401d25681a4e7a3462ef1
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Updated to 5.4.2\n * The 'exec' and 'command' precommand modifiers,\
\ and options to\n them, are now parsed after parameter expansion.\n * Functions\
\ executed by ZLE widgets no longer have their standard\n input closed, but\
\ redirected from /dev/null instead.\n * There is an option WARN_NESTED_VAR,\
\ a companion to the existing\n WARN_CREATE_GLOBAL that causes a warning if\
\ a function updates a\n variable from an enclosing scope without using typeset\
\ -g.\n * zmodload now has an option -s to be silent on a failure to find\n \
\ a module but still print other errors.\n- Dropped patch merged upstream:\n\
\ * fix-patchutils-completion.patch"
commit_time: 2018-02-27 14:07:11
expanded_srcmd5: 7bf3b5536471daa3fbc33720ebcb980d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: dfe156fd69b0d8d1745ecf6d6e02e047
mtime: 1519734333
name: zsh-5.4.2.tar.gz
size: 4482413
- md5: 10b4764a0350d83198142ce09cc99b63
mtime: 1519734333
name: zsh-5.4.2.tar.gz.asc
size: 473
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 42e088293cb7dd58b871e8ea373965f1
mtime: 1519734333
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 34332
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1718
- md5: f72350f79eca0a08a490fd920a7829f9
mtime: 1519734333
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8141
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 1981ade0ca8bcf73a50e57d12301a8e8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: kbabioch
number: 580579
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:kbabioch:branches:shells
source_rev: '3'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 184.0
unexpanded_srcmd5: 0fea226633a6bde3f961c197b0b61d9f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 80.0
commit_time: 2018-03-01 12:02:03
expanded_srcmd5: ffdaa8fa62ad85ca45374767962b5c9a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: dfe156fd69b0d8d1745ecf6d6e02e047
mtime: 1519734333
name: zsh-5.4.2.tar.gz
size: 4482413
- md5: 10b4764a0350d83198142ce09cc99b63
mtime: 1519734333
name: zsh-5.4.2.tar.gz.asc
size: 473
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 42e088293cb7dd58b871e8ea373965f1
mtime: 1519734333
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 34332
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1718
- md5: f72350f79eca0a08a490fd920a7829f9
mtime: 1519734333
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8141
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 1981ade0ca8bcf73a50e57d12301a8e8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 184.08
unexpanded_srcmd5: 0fea226633a6bde3f961c197b0b61d9f
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2018-03-01 12:02:03
expanded_srcmd5: 3d696c51df9b61e6eb968b239f408ca2
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: dfe156fd69b0d8d1745ecf6d6e02e047
mtime: 1519734333
name: zsh-5.4.2.tar.gz
size: 4482413
- md5: 10b4764a0350d83198142ce09cc99b63
mtime: 1519734333
name: zsh-5.4.2.tar.gz.asc
size: 473
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 42e088293cb7dd58b871e8ea373965f1
mtime: 1519734333
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 34332
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1718
- md5: f72350f79eca0a08a490fd920a7829f9
mtime: 1519734333
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8141
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 1981ade0ca8bcf73a50e57d12301a8e8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 580596
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '184'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 185.0
unexpanded_srcmd5: d3f0ed0be8d677eb89f9f6dbeba2a087
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to 5.5\n * The effect of the NO_INTERACTIVE_COMMENTS option\
\ extends into $(...)\n and `...` command substitutions when used on the command\
\ line.\n * Dropped patches, which are included upstream now:\n - zsh-CVE-2018-1071.patch\n\
\ - zsh-CVE-2018-1083.patch\n * Fixes a buffer overflow in utils.c:checkmailpath()\
\ that can lead to\n local arbitrary code execution (CVE-2018-1100 bnc#1089030)\n\
\n- Added zsh-CVE-2018-1071.patch: Fixed a stack-based buffer overflow\n in exec.c:hashcmd()\
\ (CVE-2018-1071 bnc#1084656)\n- Added zsh-CVE-2018-1083.patch: Fixed a stack-based\
\ buffer overflow\n in gen_matches_files() at compctl.c (CVE-2018-1083 bnc#1087026)\n\
- Cleaned up spec file with spec-cleaner"
commit_time: 2018-04-12 09:18:31
expanded_srcmd5: 751f6888973b377baae6f53dd1b0aad9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2430c85bd128c59f5c0806ef00d3ea8d
mtime: 1523433151
name: zsh-5.5.tar.gz
size: 4576506
- md5: e328d710dab08b85df0c5b3cc314f7c7
mtime: 1523433151
name: zsh-5.5.tar.gz.asc
size: 473
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 083295c4ea37184584723a026d4b0d63
mtime: 1523433151
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 35270
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1718
- md5: 81c15a5a7658b314d73bab31d8d0a8fb
mtime: 1523433152
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8044
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 854e11ba0f3517358243e53a0fbdc8f7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: kbabioch
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 595518
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: home:kbabioch:branches:shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '4'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 186.0
unexpanded_srcmd5: b3ba74d247e27497f693d8244ccc1597
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Update RPM groups.'
commit_time: 2018-04-12 13:48:18
expanded_srcmd5: d3da58a8e46edb4279f7a5609aff5c17
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2430c85bd128c59f5c0806ef00d3ea8d
mtime: 1523433151
name: zsh-5.5.tar.gz
size: 4576506
- md5: e328d710dab08b85df0c5b3cc314f7c7
mtime: 1523433151
name: zsh-5.5.tar.gz.asc
size: 473
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6d9d12882367c941f04e65cfc1e96fb7
mtime: 1523533099
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 35408
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1718
- md5: cb032e2a26137c38cfd941cac3777562
mtime: 1523533099
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8049
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c75a1a1830effcab26c6c640004c9f13
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: jengelh
number: 595954
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:jengelh:branches:shells
source_rev: '2'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 187.0
unexpanded_srcmd5: 66bc907b7e0140f6f674886b6587ff5d
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 81.0
commit_time: 2018-04-26 13:32:32
expanded_srcmd5: c6b22bcf06e9821ad7a658ad942ce852
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2430c85bd128c59f5c0806ef00d3ea8d
mtime: 1523433151
name: zsh-5.5.tar.gz
size: 4576506
- md5: e328d710dab08b85df0c5b3cc314f7c7
mtime: 1523433151
name: zsh-5.5.tar.gz.asc
size: 473
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6d9d12882367c941f04e65cfc1e96fb7
mtime: 1523533099
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 35408
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1718
- md5: cb032e2a26137c38cfd941cac3777562
mtime: 1523533099
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8049
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c75a1a1830effcab26c6c640004c9f13
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 187.081
unexpanded_srcmd5: 66bc907b7e0140f6f674886b6587ff5d
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2018-04-26 13:32:32
expanded_srcmd5: b782134da246e52a80add57771e5fdcc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2430c85bd128c59f5c0806ef00d3ea8d
mtime: 1523433151
name: zsh-5.5.tar.gz
size: 4576506
- md5: e328d710dab08b85df0c5b3cc314f7c7
mtime: 1523433151
name: zsh-5.5.tar.gz.asc
size: 473
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6d9d12882367c941f04e65cfc1e96fb7
mtime: 1523533099
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 35408
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1718
- md5: cb032e2a26137c38cfd941cac3777562
mtime: 1523533099
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8049
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c75a1a1830effcab26c6c640004c9f13
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 595955
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: shells
source_rev: '187'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 188.0
unexpanded_srcmd5: 6fd328c54179deefb922ba477da043a3
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to 5.5.1\n * fix for a configuration problem finding singal\
\ names from (some) recent\n versions of glibc\n * minor changes"
commit_time: 2018-05-14 11:01:53
expanded_srcmd5: c289f67e614abe62102c29d9820b5e6a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 678bc037a7311a46e7fc0adca7ed8266
mtime: 1526046115
name: zsh-5.5.1.tar.gz
size: 4578700
- md5: f9c86b6d33b701c8af3bf1be87f0b0da
mtime: 1526046115
name: zsh-5.5.1.tar.gz.asc
size: 473
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 18d0b3484a7b35bf793fdf9f706bdd2f
mtime: 1526046115
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 35661
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1718
- md5: 624d83b1b8d8d7bd1847ada9e0255a7e
mtime: 1526046115
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8051
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 05315558e7ee9013f616212e8d0fd467
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: kbabioch
number: 606455
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:kbabioch:branches:shells
source_rev: '2'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 189.0
unexpanded_srcmd5: 674cb4d31527d024d118c537a931ae61
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 82.0
commit_time: 2018-05-16 11:24:02
expanded_srcmd5: 148eae8f78f48a68315162deddab22af
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 678bc037a7311a46e7fc0adca7ed8266
mtime: 1526046115
name: zsh-5.5.1.tar.gz
size: 4578700
- md5: f9c86b6d33b701c8af3bf1be87f0b0da
mtime: 1526046115
name: zsh-5.5.1.tar.gz.asc
size: 473
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 18d0b3484a7b35bf793fdf9f706bdd2f
mtime: 1526046115
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 35661
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1718
- md5: 624d83b1b8d8d7bd1847ada9e0255a7e
mtime: 1526046115
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8051
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 05315558e7ee9013f616212e8d0fd467
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 189.082
unexpanded_srcmd5: 674cb4d31527d024d118c537a931ae61
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: baserev update by copy to link target
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2018-05-16 11:24:02
expanded_srcmd5: b34eeca2700d923f914404957a6f2ac1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 678bc037a7311a46e7fc0adca7ed8266
mtime: 1526046115
name: zsh-5.5.1.tar.gz
size: 4578700
- md5: f9c86b6d33b701c8af3bf1be87f0b0da
mtime: 1526046115
name: zsh-5.5.1.tar.gz.asc
size: 473
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 18d0b3484a7b35bf793fdf9f706bdd2f
mtime: 1526046115
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 35661
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1718
- md5: 624d83b1b8d8d7bd1847ada9e0255a7e
mtime: 1526046115
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8051
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 05315558e7ee9013f616212e8d0fd467
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 606966
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '189'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 190.0
unexpanded_srcmd5: 161bb83bc8c27a562104293602e6da3b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '-'
commit_time: 2018-09-04 18:12:37
expanded_srcmd5: 9b4cb36678b652e0ecd394a1dc4e0f63
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 4890f422e6f3c5127a19c8f6b867f292
mtime: 1536077556
name: zsh-5.6.tar.xz
size: 3080856
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d87dc4129dba80619bdc506a7083e942
mtime: 1536077556
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 35912
- md5: e7d0ff2e65444f474dfa5b3ac333fcc2
mtime: 1449699865
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1718
- md5: f1eba820f75b0d69812542a2880d4884
mtime: 1536077557
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7917
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: f757ac7f95de4a7e98352e6ba40fc49d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 191.0
unexpanded_srcmd5: cafd00d9b81a3ce2fa1f911bb08a180d
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '-'
commit_time: 2018-09-05 09:39:31
expanded_srcmd5: 4b53ad4e71781766564d7dfc3c4565ea
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 4890f422e6f3c5127a19c8f6b867f292
mtime: 1536077556
name: zsh-5.6.tar.xz
size: 3080856
- md5: 1aa29cd686e88b8c92120c69f0c60ab4
mtime: 1536133170
name: zsh-5.6.tar.xz.asc
size: 1276
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d87dc4129dba80619bdc506a7083e942
mtime: 1536077556
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 35912
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 7c2fa5e03d952a91e8a143679a0797dd
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7880
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 0517e2cbc1da400415a9530c7059bde4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 192.0
unexpanded_srcmd5: f3a750fbacc7edd3cb23ce310794a60c
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: ' * Switch to -fstack-protector-strong'
commit_time: 2018-09-05 10:59:19
expanded_srcmd5: 70191edfdc4886c99d72d22ad53040b0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: 4890f422e6f3c5127a19c8f6b867f292
mtime: 1536077556
name: zsh-5.6.tar.xz
size: 3080856
- md5: 1aa29cd686e88b8c92120c69f0c60ab4
mtime: 1536133170
name: zsh-5.6.tar.xz.asc
size: 1276
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 4ac148fe0872a8eaf177026fc75b0d05
mtime: 1536137959
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 35951
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 43a5742b4a7dfbebaad8521df6c75c04
mtime: 1536137959
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7979
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: e466f921a880ab19c3252aff7cce000d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 193.0
unexpanded_srcmd5: 753be37cbc7ebc1fc084c016f6ba3762
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '-'
commit_time: 2018-09-05 15:37:39
expanded_srcmd5: 325f36e7ef43f0188bf7dde0211993a9
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 4890f422e6f3c5127a19c8f6b867f292
mtime: 1536077556
name: zsh-5.6.tar.xz
size: 3080856
- md5: 1aa29cd686e88b8c92120c69f0c60ab4
mtime: 1536133170
name: zsh-5.6.tar.xz.asc
size: 1276
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 9d7a405163fd49184f2410269139a51c
mtime: 1536154659
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 35983
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 43a5742b4a7dfbebaad8521df6c75c04
mtime: 1536137959
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7979
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 56f39c49f37179f52679be2ec0dece86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 194.0
unexpanded_srcmd5: 0e1580a577595e103715cb0e068f7f3c
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '-'
commit_time: 2018-09-05 16:37:31
expanded_srcmd5: 4035bb062d1fd80d72fbf56fa08b7d6d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 4890f422e6f3c5127a19c8f6b867f292
mtime: 1536077556
name: zsh-5.6.tar.xz
size: 3080856
- md5: 1aa29cd686e88b8c92120c69f0c60ab4
mtime: 1536133170
name: zsh-5.6.tar.xz.asc
size: 1276
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 519968ed0a8ed6cb46b991516d081641
mtime: 1536158251
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36151
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 43a5742b4a7dfbebaad8521df6c75c04
mtime: 1536137959
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7979
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c97047f0bf3e1e013a2eb5137f8280e0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 195.0
unexpanded_srcmd5: a11c2f5eccc671559dc0dbd130fb72b4
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 83.0
commit_time: 2018-09-07 15:35:17
expanded_srcmd5: 1ee19164d1784271d4acc95980b3fece
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 4890f422e6f3c5127a19c8f6b867f292
mtime: 1536077556
name: zsh-5.6.tar.xz
size: 3080856
- md5: 1aa29cd686e88b8c92120c69f0c60ab4
mtime: 1536133170
name: zsh-5.6.tar.xz.asc
size: 1276
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 519968ed0a8ed6cb46b991516d081641
mtime: 1536158251
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36151
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 43a5742b4a7dfbebaad8521df6c75c04
mtime: 1536137959
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7979
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c97047f0bf3e1e013a2eb5137f8280e0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 195.083
unexpanded_srcmd5: a11c2f5eccc671559dc0dbd130fb72b4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2018-09-07 15:35:17
expanded_srcmd5: 67b01789279ed2cdad8a11bbb73b3bc5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 4890f422e6f3c5127a19c8f6b867f292
mtime: 1536077556
name: zsh-5.6.tar.xz
size: 3080856
- md5: 1aa29cd686e88b8c92120c69f0c60ab4
mtime: 1536133170
name: zsh-5.6.tar.xz.asc
size: 1276
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 519968ed0a8ed6cb46b991516d081641
mtime: 1536158251
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36151
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 43a5742b4a7dfbebaad8521df6c75c04
mtime: 1536137959
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7979
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c97047f0bf3e1e013a2eb5137f8280e0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 633489
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '195'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 196.0
unexpanded_srcmd5: 374aae85f38b54a0e830678e8ae49515
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.6.1\n * Fix packaging issue that broke runhelp\n\
\ * Fix a regression with pipelines getting backgrounded and emitting SIGTTOU"
commit_time: 2018-09-11 13:32:01
expanded_srcmd5: ebf7cd27071efcd28f2d240e3a551167
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: f7b8145d2c54ef53a093bbbf4b127af7
mtime: 1536648923
name: zsh-5.6.1.tar.xz
size: 3076732
- md5: 015f9affe87c125d546f165b632cb4e2
mtime: 1536648924
name: zsh-5.6.1.tar.xz.asc
size: 1276
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 3408fe443930086fa918ff0cd20ebe79
mtime: 1536648924
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36433
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 937e48807a1ef9eb944159c8e9f34602
mtime: 1536648924
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7981
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: f29b6354e872af3c593f090b09ea2f80
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: kbabioch
number: 634881
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:kbabioch:branches:shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_rev: '2'
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 197.0
unexpanded_srcmd5: 2771d881406fa8fe6a5db6377f9dc470
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '-'
commit_time: 2018-09-11 13:32:24
expanded_srcmd5: 0cf7dcfcd709e64c772f1cfd703c30ee
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: f7b8145d2c54ef53a093bbbf4b127af7
mtime: 1536648923
name: zsh-5.6.1.tar.xz
size: 3076732
- md5: 015f9affe87c125d546f165b632cb4e2
mtime: 1536648924
name: zsh-5.6.1.tar.xz.asc
size: 1276
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 3408fe443930086fa918ff0cd20ebe79
mtime: 1536648924
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36433
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 51dce9c230dc4f87a0d43f15d3522264
mtime: 1536665542
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7889
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 70fbcff0a363cc8b093bb8ff4956a8ba
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 198.0
unexpanded_srcmd5: bb213a68398f2a9d2630f38b0bd4f3ec
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Updateo to version 5.6.2\n * Fix another SIGTTOU case.\n * Fix SIGWINCH\
\ being ignored when zsh is not in the foreground."
commit_time: 2018-09-18 10:17:14
expanded_srcmd5: 75755c44d20b685e6d6a03871495f905
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 540673bf823d2e13806ac0395caa8345
mtime: 1537128881
name: zsh-5.6.2.tar.xz
size: 3077368
- md5: a3b09dbf98e917b33dcac74604fbfe10
mtime: 1537128881
name: zsh-5.6.2.tar.xz.asc
size: 821
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a979a9d5bd8840ef45074c7b9ab9773d
mtime: 1537128881
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36691
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 887122b0be8ff982bcd97e08c85fc6e0
mtime: 1537128881
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7889
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 4bdc85b2d710e4f713cda1fadc4957ce
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: kbabioch
number: 635960
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:kbabioch:branches:shells
source_rev: '2'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 199.0
unexpanded_srcmd5: 30fb40ed8f7dffb1ee4a5e67c2f03ef3
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 84.0
commit_time: 2018-09-18 11:39:51
expanded_srcmd5: 292badb5cbcda006e622804d8a7c1b7b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 540673bf823d2e13806ac0395caa8345
mtime: 1537128881
name: zsh-5.6.2.tar.xz
size: 3077368
- md5: a3b09dbf98e917b33dcac74604fbfe10
mtime: 1537128881
name: zsh-5.6.2.tar.xz.asc
size: 821
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a979a9d5bd8840ef45074c7b9ab9773d
mtime: 1537128881
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36691
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 887122b0be8ff982bcd97e08c85fc6e0
mtime: 1537128881
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7889
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 4bdc85b2d710e4f713cda1fadc4957ce
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 199.084
unexpanded_srcmd5: 30fb40ed8f7dffb1ee4a5e67c2f03ef3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2018-09-18 11:39:51
expanded_srcmd5: 83f8e9d7465fe65ec81575f8d7914f1d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 540673bf823d2e13806ac0395caa8345
mtime: 1537128881
name: zsh-5.6.2.tar.xz
size: 3077368
- md5: a3b09dbf98e917b33dcac74604fbfe10
mtime: 1537128881
name: zsh-5.6.2.tar.xz.asc
size: 821
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a979a9d5bd8840ef45074c7b9ab9773d
mtime: 1537128881
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36691
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 887122b0be8ff982bcd97e08c85fc6e0
mtime: 1537128881
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7889
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 4bdc85b2d710e4f713cda1fadc4957ce
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 636300
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '199'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 200.0
unexpanded_srcmd5: 6a26fca5a471bc0dc0cc509882554643
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '-'
commit_time: 2018-09-18 11:49:02
expanded_srcmd5: 0be4c9662af75cedf687ac6768a45202
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 540673bf823d2e13806ac0395caa8345
mtime: 1537128881
name: zsh-5.6.2.tar.xz
size: 3077368
- md5: a3b09dbf98e917b33dcac74604fbfe10
mtime: 1537128881
name: zsh-5.6.2.tar.xz.asc
size: 821
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 5d3fc1766b51f1046b13a599ead06d66
mtime: 1537264138
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36690
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: d37af61f6e703d7111b02625324e6291
mtime: 1537264140
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7890
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 290be5988d23fb3dd4a125d3895d588a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 201.0
unexpanded_srcmd5: 2d777e6677aee8b812742523bed27b1a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Unbreak Leap 42.3 compilation'
commit_time: 2018-09-21 11:29:49
expanded_srcmd5: 77d4b9063645d86b0f239e69952f2985
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 540673bf823d2e13806ac0395caa8345
mtime: 1537128881
name: zsh-5.6.2.tar.xz
size: 3077368
- md5: a3b09dbf98e917b33dcac74604fbfe10
mtime: 1537128881
name: zsh-5.6.2.tar.xz.asc
size: 821
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2ceec3757bf465ee58a653e762399824
mtime: 1537522189
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36858
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 0715e41b2b3671c4842183ff65677326
mtime: 1537522189
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8020
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: d5f1be96b97956d30c0050615b7494a3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 202.0
unexpanded_srcmd5: 0801c6fe11f3996160f5e08768619583
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 85.0
commit_time: 2018-10-01 09:04:03
expanded_srcmd5: f46ae1c19cd1b2294fedcdd02c8a0f84
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 540673bf823d2e13806ac0395caa8345
mtime: 1537128881
name: zsh-5.6.2.tar.xz
size: 3077368
- md5: a3b09dbf98e917b33dcac74604fbfe10
mtime: 1537128881
name: zsh-5.6.2.tar.xz.asc
size: 821
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2ceec3757bf465ee58a653e762399824
mtime: 1537522189
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36858
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 0715e41b2b3671c4842183ff65677326
mtime: 1537522189
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8020
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: d5f1be96b97956d30c0050615b7494a3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 202.085
unexpanded_srcmd5: 0801c6fe11f3996160f5e08768619583
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2018-10-01 09:04:03
expanded_srcmd5: 5145852aba6e9e79863ff69d5e3506c3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 540673bf823d2e13806ac0395caa8345
mtime: 1537128881
name: zsh-5.6.2.tar.xz
size: 3077368
- md5: a3b09dbf98e917b33dcac74604fbfe10
mtime: 1537128881
name: zsh-5.6.2.tar.xz.asc
size: 821
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2ceec3757bf465ee58a653e762399824
mtime: 1537522189
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 36858
- md5: 05cad71c8355dda6cb81538d1eca4ada
mtime: 1536133171
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 9441
- md5: 0715e41b2b3671c4842183ff65677326
mtime: 1537522189
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8020
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: d5f1be96b97956d30c0050615b7494a3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 637013
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: shells
source_rev: '202'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 203.0
unexpanded_srcmd5: 73fe76ebba15e517c27acee086091d5e
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.7\n * Support for 24-bit true color terminals has\
\ been added.\n Hex triplets can be used when specifying colours for prompts\n\
\ and line editor highlighting. On 88 and 256 colour terminals,\n a new\
\ zsh/nearcolor module allows colours specified with hex\n triplets to be matched\
\ against the nearest available colour.\n * The zsh/datetime module's strftime\
\ builtin now accepts an\n argument specifying the nanoseconds time component;\
\ both\n arguments can be omitted to use the current time."
commit_time: 2019-01-28 12:07:38
expanded_srcmd5: 0ad49169c04d4b89193b2cbc88d7e4cb
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: 4f855abd9be566bcb204e407cf571d09
mtime: 1548415942
name: zsh-5.7.tar.xz
size: 3124708
- md5: b1ef125b6f753bb68ba8c0ca558633c8
mtime: 1548415942
name: zsh-5.7.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: be3e921e0c9bbdf7f826198342e8b601
mtime: 1548415942
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 37515
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7693c513a78384ca872cf8d966cec8eb
mtime: 1548415942
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8094
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 96c6b4babb91f52151f11ba345f033ec
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 668614
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:namtrac:branches:shells
source_rev: '2'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 204.0
unexpanded_srcmd5: ccb83d53df42aedab0b29495e13a1dd5
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.7.1\n * This release contains fixes for the two\
\ regressions reported\n with VCS_Info and prompt colour sequences."
commit_time: 2019-02-04 14:22:29
expanded_srcmd5: 938952648b9615e575803253f37ff07d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 374f9fdd121b5b90e07abfcad7df0627
mtime: 1549286549
name: zsh-5.7.1.tar.xz
size: 3126308
- md5: 877554b2be677f34e8c8657a884f3e05
mtime: 1549286549
name: zsh-5.7.1.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b6f19dc4caf1ec2dc6899ce7ce733ea3
mtime: 1549286549
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 37788
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d58e44ee47cc7540040cb7ffde36a868
mtime: 1549286549
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8096
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: a19366bda32fe0f0cf6428975b695c85
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 205.0
unexpanded_srcmd5: c92b3ad3dcedcd283835002021d0d4d0
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 86.0
commit_time: 2019-02-04 21:10:56
expanded_srcmd5: 70dd46724f928c9ad018d753a01993c8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 374f9fdd121b5b90e07abfcad7df0627
mtime: 1549286549
name: zsh-5.7.1.tar.xz
size: 3126308
- md5: 877554b2be677f34e8c8657a884f3e05
mtime: 1549286549
name: zsh-5.7.1.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b6f19dc4caf1ec2dc6899ce7ce733ea3
mtime: 1549286549
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 37788
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d58e44ee47cc7540040cb7ffde36a868
mtime: 1549286549
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8096
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: a19366bda32fe0f0cf6428975b695c85
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 205.086
unexpanded_srcmd5: c92b3ad3dcedcd283835002021d0d4d0
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: baserev update by copy to link target
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2019-02-04 21:10:57
expanded_srcmd5: 6a4e089f2632a68c9eccdd724cb8eab6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 374f9fdd121b5b90e07abfcad7df0627
mtime: 1549286549
name: zsh-5.7.1.tar.xz
size: 3126308
- md5: 877554b2be677f34e8c8657a884f3e05
mtime: 1549286549
name: zsh-5.7.1.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b6f19dc4caf1ec2dc6899ce7ce733ea3
mtime: 1549286549
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 37788
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d58e44ee47cc7540040cb7ffde36a868
mtime: 1549286549
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8096
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: a19366bda32fe0f0cf6428975b695c85
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
request:
creator: namtrac
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
number: 671123
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '205'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 206.0
unexpanded_srcmd5: a5cdd348dcd10be508fc5d1c7a7f46fc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: buildservice-autocommit
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.8~pre1 (5.7.1-test-1)\n * Please see the included\
\ NEWS for new functionality"
commit_time: 2019-12-16 11:14:36
expanded_srcmd5: 3a1198bba119b35167fdcbebd1e2cb66
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6df4bb0391be5b36002950eb80b5f7cb
mtime: 1576491275
name: zsh-5.7.1-test-1.tar.xz
size: 3176336
- md5: f7afe9867fa61912e5162648e47baadb
mtime: 1576491275
name: zsh-5.7.1-test-1.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 193a27d87f715d2c619d7926bae6f89d
mtime: 1576491276
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 38022
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e00e56e17370e3f3e498431bbc16e36f
mtime: 1576491276
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8163
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 027338bf4ff4a2a3c25f67ef34313de6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 207.0
unexpanded_srcmd5: be7eb551e11981419f19ee952066802c
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: " * The zsh/zutil module's zparseopts builtin learnt an -F option to abort\n\
\ parsing when an unrecognised option-like parameter is encountered.\n * The\
\ zsh/files module gained a chmod builtin.\n * Several changes have been made\
\ to the way completion functions track\n 'precommands' (such as `command`\
\ and `env`) and determine whether the\n command being completed for is a shell\
\ builtin. Developers of completion\n functions may wish to familiarise themselves\
\ with `_normal -p` and\n `_pick_variant -b`.\n * The option CD_SILENT was\
\ added to suppress all output from cd (whether\n explicit or implicit with\
\ AUTO_CD). It is disabled by default.\n * The compadd builtin's -o option now\
\ takes an optional argument to\n specify the order of completion matches.\
\ This affects the display\n of candidate matches and the order in which they\
\ are selected when\n cycling between them using menu completion.\n * The\
\ :h and :t modifiers in parameter expansion (if braces are present),\n glob\
\ qualifiers and history expansion may take following decimal digit\n arguments\
\ in order to keep that many leading or trailing path components\n instead\
\ of the defaults of all but one (:h) and one (:t). In an absolute\n path\
\ the leading '/' counts as one component.\n * The functions builtin gained a\
\ -c option to efficiently copy functions.\n- See included ChangeLog for the complete\
\ list of changes."
commit_time: 2019-12-16 11:20:48
expanded_srcmd5: edb705b75c673b34f5f06c2ecea9800c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6df4bb0391be5b36002950eb80b5f7cb
mtime: 1576491275
name: zsh-5.7.1-test-1.tar.xz
size: 3176336
- md5: f7afe9867fa61912e5162648e47baadb
mtime: 1576491275
name: zsh-5.7.1-test-1.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: dcc1aaee506223fccd0fa0b58085a5cb
mtime: 1576491648
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 39373
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e00e56e17370e3f3e498431bbc16e36f
mtime: 1576491276
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8163
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: d8aae5f0d74dafc5f1d15190eeac3797
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 208.0
unexpanded_srcmd5: 5aba599adac0e1c065ebfb3a8387ee2f
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Add 1baf0d1f553631ecb641e98f4bf48bc2a44e5b82.patch to fix a\n re-entrancy\
\ problem."
commit_time: 2019-12-16 16:11:39
expanded_srcmd5: 12c597ecc794e0764dac7d58085f1608
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 164953275ded2c6ea5959266c2aa9b98
mtime: 1576509099
name: 1baf0d1f553631ecb641e98f4bf48bc2a44e5b82.patch
size: 2658
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6df4bb0391be5b36002950eb80b5f7cb
mtime: 1576491275
name: zsh-5.7.1-test-1.tar.xz
size: 3176336
- md5: f7afe9867fa61912e5162648e47baadb
mtime: 1576491275
name: zsh-5.7.1-test-1.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e492fe9fb6fa3b1b04cfcb3011140a71
mtime: 1576509099
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 39593
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 0849a1e27347dc8a476179c36b4075a0
mtime: 1576509099
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8238
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 1314b8a7600dca02e6e75f7a6be08bc5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 209.0
unexpanded_srcmd5: 59f43de19bcd2e14dec521ca6adcd04e
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.8~pre2 (5.7.1-test-2)\n- Drop 1baf0d1f553631ecb641e98f4bf48bc2a44e5b82.patch,\
\ fixed\n upstream."
commit_time: 2019-12-22 10:27:57
expanded_srcmd5: 4737d14f26cab8946737c73706e8adca
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b82302ee34c9fd53afc247160f2e581a
mtime: 1577006875
name: zsh-5.7.1-test-2.tar.xz
size: 3180532
- md5: 00cffae3c868465f9e2aca90de129876
mtime: 1577006876
name: zsh-5.7.1-test-2.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 67f6cb55fb132d4f408abdab29914852
mtime: 1577006876
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 39845
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e2f1e3aeed148a7b58b7d3c77dfd1a64
mtime: 1577006877
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8163
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 29840d573e65443efa0b3fd060bfc547
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 210.0
unexpanded_srcmd5: b62eb3e058a1f7869890bd778200bd00
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 87.0
commit_time: 2019-12-23 22:42:01
expanded_srcmd5: 23f3ab2bc38baa37d9a51eb7e15ecdc7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b82302ee34c9fd53afc247160f2e581a
mtime: 1577006875
name: zsh-5.7.1-test-2.tar.xz
size: 3180532
- md5: 00cffae3c868465f9e2aca90de129876
mtime: 1577006876
name: zsh-5.7.1-test-2.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 67f6cb55fb132d4f408abdab29914852
mtime: 1577006876
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 39845
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e2f1e3aeed148a7b58b7d3c77dfd1a64
mtime: 1577006877
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8163
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 29840d573e65443efa0b3fd060bfc547
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 210.087
unexpanded_srcmd5: b62eb3e058a1f7869890bd778200bd00
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: baserev update by copy to link target
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2019-12-23 22:42:01
expanded_srcmd5: 02097ea926292642c90e81e6f55d8b69
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b82302ee34c9fd53afc247160f2e581a
mtime: 1577006875
name: zsh-5.7.1-test-2.tar.xz
size: 3180532
- md5: 00cffae3c868465f9e2aca90de129876
mtime: 1577006876
name: zsh-5.7.1-test-2.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 67f6cb55fb132d4f408abdab29914852
mtime: 1577006876
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 39845
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e2f1e3aeed148a7b58b7d3c77dfd1a64
mtime: 1577006877
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8163
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
files_hash: 29840d573e65443efa0b3fd060bfc547
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 758830
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '210'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 211.0
unexpanded_srcmd5: f49134538acd709812dc081fffbadf9d
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.8~pre3 (5.7.1-test-3)\n * Minor bugfixes compared\
\ to pre2"
commit_time: 2020-02-07 13:11:57
expanded_srcmd5: 0172fa42e486db4c7e0ad9718c390019
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d757e713284cfed2c68865b32b6a5743
mtime: 1581077516
name: zsh-5.7.1-test-3.tar.xz
size: 3188996
- md5: 8d7eb6a4c07d3e5ff08575355118760a
mtime: 1581077516
name: zsh-5.7.1-test-3.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 677c52627be5f5624a75238ffc064c09
mtime: 1581077516
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40060
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 385a160ec728eabbe36f605389b4ef4d
mtime: 1581077516
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8163
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7310
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 2f9c8c0f0023626dddd5b9c8a732793c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 212.0
unexpanded_srcmd5: 7ba8291568bb3a0ef0a21117e5cd8b5e
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 88.0
commit_time: 2020-02-15 22:23:25
expanded_srcmd5: 1e54505eda46fb94551decc846d16ad0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d757e713284cfed2c68865b32b6a5743
mtime: 1581077516
name: zsh-5.7.1-test-3.tar.xz
size: 3188996
- md5: 8d7eb6a4c07d3e5ff08575355118760a
mtime: 1581077516
name: zsh-5.7.1-test-3.tar.xz.asc
size: 488
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 677c52627be5f5624a75238ffc064c09
mtime: 1581077516
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40060
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1725
- md5: 385a160ec728eabbe36f605389b4ef4d
mtime: 1581077516
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8163
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 2f9c8c0f0023626dddd5b9c8a732793c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 212.088
unexpanded_srcmd5: 7ba8291568bb3a0ef0a21117e5cd8b5e
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2020-02-15 22:23:25
expanded_srcmd5: 7a2003b81026a4657b1a29f258a0a5dd
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: d757e713284cfed2c68865b32b6a5743
mtime: 1581077516
name: zsh-5.7.1-test-3.tar.xz
size: 3188996
- md5: 8d7eb6a4c07d3e5ff08575355118760a
mtime: 1581077516
name: zsh-5.7.1-test-3.tar.xz.asc
size: 488
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 677c52627be5f5624a75238ffc064c09
mtime: 1581077516
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40060
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1725
- md5: 385a160ec728eabbe36f605389b4ef4d
mtime: 1581077516
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8163
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 2f9c8c0f0023626dddd5b9c8a732793c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
request:
creator: namtrac
number: 771563
source_package: zsh
source_project: shells
source_rev: '212'
state: accepted
type: submit
rev: 213.0
unexpanded_srcmd5: 490a2ce1add5525e689cc396bf45a3d0
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Update to version 5.8\n * Fixes CVE-2019-20044"
commit_time: 2020-02-17 06:29:19
expanded_srcmd5: f124dc437eb8a9f28cc056eba0572484
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e6949a24bf93f45dc64e35f4acec92e1
mtime: 1581917359
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40244
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1725
- md5: 1d6aa472172299aadc6720ce0c2f2c45
mtime: 1581917359
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8066
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 02d2b5d4c5017547ca7de1108ea902e0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 214.0
unexpanded_srcmd5: d6b0d4657051b946e2bc1751e9eb9044
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
comment: '-'
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
commit_time: 2020-02-17 13:12:33
expanded_srcmd5: 069973155ee1d14fb2ef3ac450f59075
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 43a4fba3bbfa4b4b12f78c3969ad019a
mtime: 1581941552
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40256
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1725
- md5: 1d6aa472172299aadc6720ce0c2f2c45
mtime: 1581917359
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8066
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 4b163e04d058ed7f25d8150888a4eca6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 215.0
unexpanded_srcmd5: 4084b2f9e7b12260484666869539c42a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 89.0
commit_time: 2020-02-20 14:53:48
expanded_srcmd5: c5fbb4c7f0f1dd83754f109b3268639d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 43a4fba3bbfa4b4b12f78c3969ad019a
mtime: 1581941552
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40256
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1725
- md5: 1d6aa472172299aadc6720ce0c2f2c45
mtime: 1581917359
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8066
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 4b163e04d058ed7f25d8150888a4eca6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 215.089
unexpanded_srcmd5: 4084b2f9e7b12260484666869539c42a
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2020-02-20 14:53:48
expanded_srcmd5: c88541792eac65539c2c0c4045118e55
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 43a4fba3bbfa4b4b12f78c3969ad019a
mtime: 1581941552
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40256
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1725
- md5: 1d6aa472172299aadc6720ce0c2f2c45
mtime: 1581917359
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8066
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 4b163e04d058ed7f25d8150888a4eca6
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
request:
creator: namtrac
number: 774851
source_package: zsh
source_project: shells
source_rev: '215'
state: accepted
type: submit
rev: 216.0
unexpanded_srcmd5: 5dd3d6e995a465f5bd506f2edd5beccf
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Remove stack-protector option addition, it''s already in $optflags.'
commit_time: 2020-03-10 10:26:21
expanded_srcmd5: e21e589eb3b618043fd68a0ba49136b8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b78fc56158d6a9644682055f0c65fe65
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40457
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7911
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c7e5cab3cf46d4964ccf50ab627c7d86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
request:
creator: marxin
number: 783187
source_package: zsh
source_project: home:marxin:branches:shells
source_rev: '2'
state: accepted
type: submit
rev: 217.0
unexpanded_srcmd5: 5a75759a0f454123d09dc22059d4e747
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 90.0
commit_time: 2020-03-11 18:45:53
expanded_srcmd5: c53e1f9b252606b62a58e01e46d87c77
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b78fc56158d6a9644682055f0c65fe65
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40457
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.keyring
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7911
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c7e5cab3cf46d4964ccf50ab627c7d86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 217.09
unexpanded_srcmd5: 5a75759a0f454123d09dc22059d4e747
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2020-03-11 18:45:53
expanded_srcmd5: c18ac3da3e2a166579594f7f7236c9d7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b78fc56158d6a9644682055f0c65fe65
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40457
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7911
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: c124e19ba111adb279273c2801e09a4c
mtime: 1429699475
name: zshrc
size: 7310
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: c7e5cab3cf46d4964ccf50ab627c7d86
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
request:
creator: namtrac
number: 783235
source_package: zsh
source_project: shells
source_rev: '217'
state: accepted
type: submit
rev: 218.0
unexpanded_srcmd5: 68d4a763de1c7d7cdf0c0b9ce33d8cb2
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Stop sourcing /etc/bash.bashrc which causes problems with ls, add\n\
\ a call to manually source /etc/zsh.zshrc.local if available."
commit_time: 2020-04-08 08:08:52
expanded_srcmd5: 50498b257bc78f506ed0b54d34f46129
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 3e5514ec3a821f22db41452c7e3f307c
mtime: 1586326131
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40723
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7911
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 45b24dd95a40884324f3b362516ade14
mtime: 1586326131
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7305
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: d9971d5f3928360c68210898e3b0dd0b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 219.0
unexpanded_srcmd5: 4aa7f43e9332054f47d046b4a60bab04
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 91.0
commit_time: 2020-04-13 12:51:40
expanded_srcmd5: 7df3cf898cdd2cc0f751de4e88330c76
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 3e5514ec3a821f22db41452c7e3f307c
mtime: 1586326131
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40723
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7911
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 45b24dd95a40884324f3b362516ade14
mtime: 1586326131
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7305
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: d9971d5f3928360c68210898e3b0dd0b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 219.091
unexpanded_srcmd5: 4aa7f43e9332054f47d046b4a60bab04
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2020-04-13 12:51:41
expanded_srcmd5: 55683575f7704c282a97c73233c4e762
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 3e5514ec3a821f22db41452c7e3f307c
mtime: 1586326131
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40723
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7911
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 45b24dd95a40884324f3b362516ade14
mtime: 1586326131
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7305
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: d9971d5f3928360c68210898e3b0dd0b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
request:
creator: namtrac
number: 792416
source_package: zsh
source_project: shells
source_rev: '219'
state: accepted
type: submit
rev: 220.0
unexpanded_srcmd5: 5df9de712a983016296acda73fcc45e8
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- Add aliases from /etc/bash.bashrc into /etc/zshrc so we don't\n regress"
commit_time: 2020-04-15 11:06:05
expanded_srcmd5: 67e41d374f18b950885894c4c79d6c9a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a7e8a7b1e8a6acb4634b7d803a4c1555
mtime: 1586941565
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40932
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7911
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ffbd0d215490f7ebc2fdade4eacfa426
mtime: 1586941565
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7874
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: ab172d8c93c010602ccd2704d088f933
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 221.0
unexpanded_srcmd5: 7216a701281d866b41171e7dfb8f1490
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 92.0
commit_time: 2020-04-16 22:58:55
expanded_srcmd5: ed1fc9ea9b4fde2bad405af1be46720d
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a7e8a7b1e8a6acb4634b7d803a4c1555
mtime: 1586941565
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 40932
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
name: zsh.spec
size: 7911
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: ffbd0d215490f7ebc2fdade4eacfa426
mtime: 1586941565
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7874
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: ab172d8c93c010602ccd2704d088f933
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 221.092
unexpanded_srcmd5: 7216a701281d866b41171e7dfb8f1490
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2020-04-16 22:58:55
expanded_srcmd5: f3700f2c8510ea1c5c65db80167860c1
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: a7e8a7b1e8a6acb4634b7d803a4c1555
mtime: 1586941565
name: zsh.changes
size: 40932
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
name: zsh.spec
size: 7911
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: ffbd0d215490f7ebc2fdade4eacfa426
mtime: 1586941565
name: zshrc
size: 7874
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: ab172d8c93c010602ccd2704d088f933
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
request:
creator: namtrac
number: 794119
source_package: zsh
source_project: shells
source_rev: '221'
state: accepted
type: submit
rev: 222.0
unexpanded_srcmd5: 9af7b7af4a9aeb0681e02c921e076319
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
comment: '- Add back LS_COLORS and LS_OPTIONS'
commit_time: 2020-05-05 06:41:29
expanded_srcmd5: bd7b5fa4cf87c21413b5915a99e6d35c
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 23bfbf0b0c871105db337e8fa69b4ae4
mtime: 1588653688
name: zsh.changes
size: 41104
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
name: zsh.spec
size: 7911
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 9c0d584fbab1929d9caaf64616ad2d48
mtime: 1588653689
name: zshrc
size: 8709
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 8cf8d42a9b7717bd542820ed83e582aa
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 223.0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
unexpanded_srcmd5: 38ff3f469f658eb43e1986d65e2ff1c8
userid: namtrac
- broken: false
comment: '-'
commit_time: 2020-05-05 15:40:11
expanded_srcmd5: 398526b255e960028aafccc4ee464462
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 303054e0ef6eeb309cc9bd31d4c97d00
mtime: 1588686011
name: zsh.changes
size: 41112
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
name: zsh.spec
size: 7911
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 0fba6259f5669787782ff92e7abeb746
mtime: 1588686011
name: zshrc
size: 8867
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 042ea738ca8bef5df5e7854f6e95138c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 224.0
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
unexpanded_srcmd5: 53093d8f18d4aa3ce5c06c29f351be5b
userid: namtrac
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- Add $HOME aliases to fix regression after dropping /etc/bash.bashrc
'
commit_time: 2020-05-06 07:17:27
expanded_srcmd5: dc275ec153bf10d8a7036eb13d2cf781
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 111604bf070fafdd380d98715e98fc35
mtime: 1588709286
name: zsh.changes
size: 41323
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
name: zsh.spec
size: 7911
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 939c99c187ae38e220e9ad634eb3dfae
mtime: 1588709223
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8907
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
files_hash: 05fa5eb65d182b8841e05be47754484b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: NickLion
number: 800460
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:NickLion:shells
source_rev: '3'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 225.0
unexpanded_srcmd5: 20cd94f7b4aefec10bb7ccaf23fd101b
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 93.0
commit_time: 2020-05-08 23:00:58
expanded_srcmd5: 0b9195e89ef88c9fed89df800ce50ff4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 111604bf070fafdd380d98715e98fc35
mtime: 1588709286
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 41323
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7911
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 939c99c187ae38e220e9ad634eb3dfae
mtime: 1588709223
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8907
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
files_hash: 05fa5eb65d182b8841e05be47754484b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 225.093
unexpanded_srcmd5: 20cd94f7b4aefec10bb7ccaf23fd101b
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2020-05-08 23:00:58
expanded_srcmd5: f233974878455c8b9fcff386f65bc8ea
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 111604bf070fafdd380d98715e98fc35
mtime: 1588709286
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 41323
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7911
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 939c99c187ae38e220e9ad634eb3dfae
mtime: 1588709223
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8907
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
files_hash: 05fa5eb65d182b8841e05be47754484b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: namtrac
number: 800536
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
source_project: shells
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_rev: '225'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 226.0
unexpanded_srcmd5: c952ca0f8eed90929eacdc343be8a80e
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Missed one more alias
commit_time: 2020-05-22 16:15:58
expanded_srcmd5: 1bc8796b47a7dce49cc85a325b0ce215
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 111604bf070fafdd380d98715e98fc35
mtime: 1588709286
name: zsh.changes
size: 41323
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 791c0dad356ba21cf5deb317ed5486ed
mtime: 1583829749
name: zsh.spec
size: 7911
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
mtime: 1196723013
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
name: zshrc
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
files_hash: f697aa30011cb04927980dfe74869d11
package: zsh
project: shells
rev: 227.0
unexpanded_srcmd5: 88f56212457d35010874ff124aa36e7c
userid: namtrac
- broken: false
comment: '- Add ncurses-fix.patch in order to fix ncurses failure.
Use upstream patch.'
commit_time: 2020-08-28 10:30:41
expanded_srcmd5: da5ff79d96a9c2db27ce012c5208e9ff
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: a8e2acb46201b1f5a2543734b764a1c6
mtime: 1598597687
name: ncurses-fix.patch
size: 2509
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: f0d7436956b2f8627856df81c9d4fed7
mtime: 1598361971
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 41512
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: fbda7ba8a6efa07d4f3ddfa62fd25593
mtime: 1598361971
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7957
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
files_hash: 2f67bda66a72670ab82e7e81102e4bc5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
request:
creator: marxin
number: 830190
source_package: zsh
source_project: home:marxin:branches:shells
source_rev: '3'
state: accepted
type: submit
rev: 228.0
unexpanded_srcmd5: adfb4793e989851b3e1c00414ee78c7f
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 94.0
commit_time: 2020-10-06 17:06:09
expanded_srcmd5: 5ac8754cd8813bb124f223517b1568e4
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: a8e2acb46201b1f5a2543734b764a1c6
mtime: 1598597687
name: ncurses-fix.patch
size: 2509
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: f0d7436956b2f8627856df81c9d4fed7
mtime: 1598361971
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 41512
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: fbda7ba8a6efa07d4f3ddfa62fd25593
mtime: 1598361971
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7957
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
files_hash: 2f67bda66a72670ab82e7e81102e4bc5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 228.094
unexpanded_srcmd5: adfb4793e989851b3e1c00414ee78c7f
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2020-10-06 17:06:09
expanded_srcmd5: 9963f89cb0f4bb5f17e234cd3b1950ef
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: a8e2acb46201b1f5a2543734b764a1c6
mtime: 1598597687
name: ncurses-fix.patch
size: 2509
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: f0d7436956b2f8627856df81c9d4fed7
mtime: 1598361971
name: zsh.changes
size: 41512
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: fbda7ba8a6efa07d4f3ddfa62fd25593
mtime: 1598361971
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 7957
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
files_hash: 2f67bda66a72670ab82e7e81102e4bc5
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
request:
creator: namtrac
number: 830225
source_package: zsh
source_project: shells
source_rev: '228'
state: accepted
type: submit
rev: 229.0
unexpanded_srcmd5: fddc08305179a98f8d67276fe9d29ba9
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- prepare usrmerge (boo#1029961)'
commit_time: 2020-11-30 18:59:42
expanded_srcmd5: 9df1ad517fc9666d8ecba7a9c39461d8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: a8e2acb46201b1f5a2543734b764a1c6
mtime: 1598597687
name: ncurses-fix.patch
size: 2509
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: fea885aee6a9923e3e7873dd45c94927
mtime: 1604415550
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 41678
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: cc4dd727f21675db36df4e2ea3ac81b3
mtime: 1605885302
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8062
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
files_hash: 5cc2dd4280b976d4c11e04a7fe105aae
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
request:
creator: lnussel
number: 851919
source_package: zsh
source_project: home:lnussel:usrmove
source_rev: null
state: accepted
type: submit
rev: 230.0
unexpanded_srcmd5: 38761e1fef01e990fc93a313a4fd484c
userid: namtrac
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 95.0
commit_time: 2020-12-02 13:57:45
expanded_srcmd5: 8e6f1a81f3d5903c1106b5e9f49ee491
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: a8e2acb46201b1f5a2543734b764a1c6
mtime: 1598597687
name: ncurses-fix.patch
size: 2509
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: fea885aee6a9923e3e7873dd45c94927
mtime: 1604415550
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 41678
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: cc4dd727f21675db36df4e2ea3ac81b3
mtime: 1605885302
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8062
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
files_hash: 5cc2dd4280b976d4c11e04a7fe105aae
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 230.095
unexpanded_srcmd5: 38761e1fef01e990fc93a313a4fd484c
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2020-12-02 13:57:45
expanded_srcmd5: 36245d6b4465002bc01bc5eb77413872
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a8e2acb46201b1f5a2543734b764a1c6
mtime: 1598597687
name: ncurses-fix.patch
size: 2509
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: e02a5428620b3dd268800c7843b3dd4d
mtime: 1581917359
name: zsh-5.8.tar.xz
size: 3193284
- md5: 79d276be0816de65dd97f62becd5be98
mtime: 1581917359
name: zsh-5.8.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: fea885aee6a9923e3e7873dd45c94927
mtime: 1604415550
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 41678
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: cc4dd727f21675db36df4e2ea3ac81b3
mtime: 1605885302
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8062
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 5cc2dd4280b976d4c11e04a7fe105aae
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
request:
creator: namtrac
number: 851932
source_package: zsh
source_project: shells
source_rev: '230'
state: accepted
type: submit
rev: 231.0
unexpanded_srcmd5: 73a20b8385a977f010afe8dd56cfcbd0
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- update to 5.8.1 (bsc#1196435, CVE-2021-45444):\n * CVE-2021-45444:\
\ Some prompt expansion sequences, such as %F, support\n 'arguments' which\
\ are themselves expanded in case they contain colour\n values, etc. This additional\
\ expansion would trigger PROMPT_SUBST\n evaluation, if enabled. This could\
\ be abused to execute code the user\n didn't expect. e.g., given a certain\
\ prompt configuration, an attacker\n could trick a user into executing arbitrary\
\ code by having them check\n out a Git branch with a specially crafted name.\n\
\ This is fixed in the shell itself by no longer performing PROMPT_SUBST\n\
\ evaluation on these prompt-expansion arguments.\n Users who are concerned\
\ about an exploit but unable to update their\n binaries may apply the partial\
\ work-around described in the file\n Etc/CVE-2021-45444-VCS_Info-workaround.patch\
\ included with the shell\n source. [ Reported by RyotaK <security@ryotak.me>.\
\ Additional thanks to\n Marc Cornell\xE0 <hello@mcornella.com>. ]"
commit_time: 2022-03-25 12:28:53
expanded_srcmd5: 20d1708ef4ee9a2ee7188d03f41903a7
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a8e2acb46201b1f5a2543734b764a1c6
mtime: 1598597687
name: ncurses-fix.patch
size: 2509
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 063a98c256ee0584b3c115924e41a332
mtime: 1644825326
name: zsh-5.8.1.tar.xz
size: 3200540
- md5: 8f0910bb736c51fff575d02a389e49bb
mtime: 1644825326
name: zsh-5.8.1.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: ea40a2a4fcfb6a3ed0c7aa299c312b08
mtime: 1647806704
name: zsh.changes
size: 42817
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 6535db04b5697b61452ad3bf03b29232
mtime: 1644825327
name: zsh.spec
size: 8064
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
name: zshrc
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
files_hash: 108d3cba85c441301b8d6338eb7ace5b
package: zsh
project: shells
request:
creator: dirkmueller
number: 963340
source_package: zsh
source_project: home:dirkmueller:Factory
source_rev: '2'
state: accepted
type: submit
rev: 232.0
unexpanded_srcmd5: 809063558de81ef62085ddbd40ed3964
userid: pperego
- broken: false
comment: Updating link to change in openSUSE:Factory/zsh revision 96.0
commit_time: 2022-03-28 17:00:11
expanded_srcmd5: eb3a2222a27c47f07991bf34ee114c6b
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: a8e2acb46201b1f5a2543734b764a1c6
mtime: 1598597687
name: ncurses-fix.patch
size: 2509
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: 063a98c256ee0584b3c115924e41a332
mtime: 1644825326
name: zsh-5.8.1.tar.xz
size: 3200540
- md5: 8f0910bb736c51fff575d02a389e49bb
mtime: 1644825326
name: zsh-5.8.1.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: ea40a2a4fcfb6a3ed0c7aa299c312b08
mtime: 1647806704
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 42817
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 6535db04b5697b61452ad3bf03b29232
mtime: 1644825327
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8064
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 108d3cba85c441301b8d6338eb7ace5b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 232.096
unexpanded_srcmd5: 809063558de81ef62085ddbd40ed3964
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2022-03-28 17:00:11
expanded_srcmd5: fbb98f894e9b146ad53821c4682969df
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: a8e2acb46201b1f5a2543734b764a1c6
mtime: 1598597687
name: ncurses-fix.patch
size: 2509
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: 063a98c256ee0584b3c115924e41a332
mtime: 1644825326
name: zsh-5.8.1.tar.xz
size: 3200540
- md5: 8f0910bb736c51fff575d02a389e49bb
mtime: 1644825326
name: zsh-5.8.1.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: ea40a2a4fcfb6a3ed0c7aa299c312b08
mtime: 1647806704
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 42817
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 6535db04b5697b61452ad3bf03b29232
mtime: 1644825327
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8064
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: 108d3cba85c441301b8d6338eb7ace5b
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
request:
creator: pperego
number: 964828
source_package: zsh
source_project: shells
source_rev: 20d1708ef4ee9a2ee7188d03f41903a7
state: accepted
type: submit
rev: 233.0
unexpanded_srcmd5: 461bc2b6ff3c98044c7a971d8706ec48
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: "- update to 5.9:\n zsh 5.9 is dedicated to the memory of Sven Guckes,\
\ who was, amongst other\n things, a long-time zsh advocate. For more information,\
\ see:\n https://linuxnews.de/2022/02/sven-guckes-verstorben/\n https://groups.google.com/g/vim_announce/c/MJBKVd-xrEE/m/joVNaDgAAgAJ\n\
\ When unsetting a hash element, the string enclosed in square brackets is\n\
\ interpreted literally after any normal command-line-argument expansions.\n\
\ Thus\n unset \"hash[$key]\"\n first expands $key as usual for a double-quoted\
\ string, and then interprets\n that result as the exact hash element to unset.\
\ This differs from previous\n versions of the shell, which would also remove\
\ a leading backslash for an\n unusual subset of characters in the expansion\
\ of $key. Note this also\n means, for example, that now\n unset 'hash[ab]cd]'\n\
\ unsets the element with key \"ab]cd\" rather than silently doing nothing.\n\
\ The function command learnt a -T option to declare a function and enable\n\
\ tracing for it simultaneously.\n The option SHORT_REPEAT was added to enable\
\ the short syntax of\n SHORT_LOOPS for the repeat command only. It is disabled\
\ by default.\n The _arguments function now supports NUL-delimiting optargs in\
\ the\n opt_args array via the -0 option. Developers of completion functions\n\
\ should find this easier to handle reliably than the default\n colon-delimiting\
\ behaviour.\n The zsh/system module's `zsystem flock` command learnt an -i option\
\ to\n set the wait interval used with -t. Additionally, -t now supports\n fractional\
\ seconds.\n The option CLOBBER_EMPTY was added to enable the overwrite behaviour\n\
\ of CLOBBER for empty files only. It is disabled by default.\n A (-) expansion\
\ flag was added. It works like (n) but correctly sorts"
commit_time: 2022-05-24 19:23:34
expanded_srcmd5: b9d92abdfe63b8bf7c71388342e69981
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: 182e37ca3fe3fa6a44f69ad462c5c30e
mtime: 1652636844
name: zsh-5.9.tar.xz
size: 3332400
- md5: a19a373a7650a9a629323a4364e1bc79
mtime: 1652636844
name: zsh-5.9.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 5d670cd2425647286b81a126f4c85809
mtime: 1652636844
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 48221
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 3ab19f0f7098edc637f5e25500d03276
mtime: 1652636844
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8059
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: ae89175d8b4c0ecde5db52a3a1d5f5a3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
request:
creator: dirkmueller
number: 977384
source_package: zsh
source_project: home:dirkmueller:Factory
source_rev: '4'
state: accepted
type: submit
rev: 234.0
unexpanded_srcmd5: f115303e257e1c3504a5db6e30cfa79c
userid: pperego
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 97.0
commit_time: 2022-05-25 20:34:07
expanded_srcmd5: 36ff26b235c5df3ddeb2e487affd0979
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: 182e37ca3fe3fa6a44f69ad462c5c30e
mtime: 1652636844
name: zsh-5.9.tar.xz
size: 3332400
- md5: a19a373a7650a9a629323a4364e1bc79
mtime: 1652636844
name: zsh-5.9.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 5d670cd2425647286b81a126f4c85809
mtime: 1652636844
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 48221
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 3ab19f0f7098edc637f5e25500d03276
mtime: 1652636844
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8059
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: ae89175d8b4c0ecde5db52a3a1d5f5a3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 234.097
unexpanded_srcmd5: f115303e257e1c3504a5db6e30cfa79c
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
commit_time: 2022-05-25 20:34:07
expanded_srcmd5: 13ebd05cd74728afc9e99d327209815a
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zprofile.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 375
- md5: 182e37ca3fe3fa6a44f69ad462c5c30e
mtime: 1652636844
name: zsh-5.9.tar.xz
size: 3332400
- md5: a19a373a7650a9a629323a4364e1bc79
mtime: 1652636844
name: zsh-5.9.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: 5d670cd2425647286b81a126f4c85809
mtime: 1652636844
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 48221
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 3ab19f0f7098edc637f5e25500d03276
mtime: 1652636844
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8059
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zshrc.rhs
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 1135
files_hash: ae89175d8b4c0ecde5db52a3a1d5f5a3
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
request:
creator: pperego
number: 979023
source_package: zsh
source_project: shells
source_rev: b9d92abdfe63b8bf7c71388342e69981
state: accepted
type: submit
rev: 235.0
unexpanded_srcmd5: 07d7282f1b6adc6598029eb5245e50cb
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: '- add egrep-deprecation.patch (bsc#1203241)'
commit_time: 2022-09-13 10:12:36
expanded_srcmd5: 4097e03edf23505d3129bdfa412e0399
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 3896df2dd48cc8d813ed5ae050ebdbbc
mtime: 1662987947
name: egrep-deprecation.patch
size: 883
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: 182e37ca3fe3fa6a44f69ad462c5c30e
mtime: 1652636844
name: zsh-5.9.tar.xz
size: 3332400
- md5: a19a373a7650a9a629323a4364e1bc79
mtime: 1652636844
name: zsh-5.9.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bf8d364cf9f23065f6bbba63930bdbc6
mtime: 1662987948
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 48400
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 692aed08bb8ddab9a86883b0d5d31e8c
mtime: 1662989807
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8195
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
name: zshrc
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 1372ffe69a925e1acc78948fc13279f8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
creator: dirkmueller
number: 1002958
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
source_package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
source_project: home:dirkmueller:Factory
source_rev: '7'
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 236.0
unexpanded_srcmd5: 8ee7601721b4ef23abbdc2ec642bef6f
userid: pperego
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: Updating link to change in openSUSE:Factory/zsh revision 98.0
commit_time: 2022-09-14 13:44:33
expanded_srcmd5: 85038f6bac15fafbbf7d26332bec45bf
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 3896df2dd48cc8d813ed5ae050ebdbbc
mtime: 1662987947
name: egrep-deprecation.patch
size: 883
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 182e37ca3fe3fa6a44f69ad462c5c30e
mtime: 1652636844
name: zsh-5.9.tar.xz
size: 3332400
- md5: a19a373a7650a9a629323a4364e1bc79
mtime: 1652636844
name: zsh-5.9.tar.xz.asc
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: bf8d364cf9f23065f6bbba63930bdbc6
mtime: 1662987948
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.changes
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 48400
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
- md5: 692aed08bb8ddab9a86883b0d5d31e8c
mtime: 1662989807
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
name: zsh.spec
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
size: 8195
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
name: zshrc
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 1372ffe69a925e1acc78948fc13279f8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
rev: 236.098
unexpanded_srcmd5: 8ee7601721b4ef23abbdc2ec642bef6f
userid: buildservice-autocommit
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
- broken: false
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
comment: baserev update by copy to link target
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
commit_time: 2022-09-14 13:44:33
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
expanded_srcmd5: f6047d468d4c226475523d87f5acbf01
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
files:
- md5: b47fde291a7ff0d6edc9151f3af2ce2d
mtime: 1309365132
name: dotzshrc.rh
size: 658
- md5: 3896df2dd48cc8d813ed5ae050ebdbbc
mtime: 1662987947
name: egrep-deprecation.patch
size: 883
- md5: 7118e89fe00f5b94b972f84f2407b956
mtime: 1363861230
name: trim-unneeded-completions.patch
size: 739
- md5: 98c085da4fee043f2a715f5530fc1b5f
mtime: 1309349171
name: zlogin.rhs
size: 252
- md5: dcf0a7daf3a3ca2df4c8f5b67686298c
mtime: 1309349171
name: zlogout.rhs
size: 86
- md5: fb654ba8fc4f1bc4a15e16bebb7d9944
mtime: 1481709716
name: zprofile
size: 198
- md5: a5e93cd6880da04a63fc4fcaaa03987f
mtime: 1397825264
name: zprofile.rhs
size: 375
- md5: 182e37ca3fe3fa6a44f69ad462c5c30e
mtime: 1652636844
name: zsh-5.9.tar.xz
size: 3332400
- md5: a19a373a7650a9a629323a4364e1bc79
mtime: 1652636844
name: zsh-5.9.tar.xz.asc
size: 488
- md5: 3c1f205ef942d1de79f94b0248bc452e
mtime: 1430638601
name: zsh-osc-completion.patch
size: 767
- md5: bf8d364cf9f23065f6bbba63930bdbc6
mtime: 1662987948
name: zsh.changes
size: 48400
- md5: af5697adf0ba2cb3b6ec332d0788be19
mtime: 1548415942
name: zsh.keyring
size: 1725
- md5: 692aed08bb8ddab9a86883b0d5d31e8c
mtime: 1662989807
name: zsh.spec
size: 8195
- md5: 955d8339c699fc1b1c1e16a9c80ef86c
mtime: 1196723013
name: zshenv
size: 45
- md5: 2617058a092497d98fc4ef54a7291704
mtime: 1309349173
name: zshenv.rhs
size: 304
- md5: 6bdbff657e2d657d27491e85d34f8f51
mtime: 1590156958
name: zshrc
size: 8934
- md5: 1be521bc4a9380e9e4dc65dae727fe28
mtime: 1458654861
name: zshrc.rhs
size: 1135
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
files_hash: 1372ffe69a925e1acc78948fc13279f8
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
package: zsh
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
project: shells
Add the capability to export the package data as test fixture
2022-10-21 09:48:31 +02:00
request:
creator: pperego
number: 1003249
source_package: zsh
source_project: shells
source_rev: 4097e03edf23505d3129bdfa412e0399
state: accepted
type: submit
Create fake revisions for every commit in the base of a linked package This is a rather complex operation, but whenever a package changes in Factory, the inherited package gets a shadow revision consisting of the 3-way merge. If this happens due to a request being accepted, this is actually in most cases also commited by 'buildservice-autocommit', so we're making sure this is always happening (and are actually duplicating revisions in cases that we filter out later as empty commits). To differenciate the fake revisions from the real revisions, I add a fraction part
2022-10-24 20:21:53 +02:00
rev: 237.0
unexpanded_srcmd5: 0ac640960fd64f758ca0e5c16362c520
userid: buildservice-autocommit
Copy Permalink