http://bugzilla.opensuse.org/show_bug.cgi?id=1047218
Bug ID: 1047218
Summary: trackerbug: packages do not build reproducibly from
including build time
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: All
OS: SUSE Other
Status: CONFIRMED
Severity: Normal
Priority: P5 - None
Component: Development
Assignee: bwiedemann(a)suse.com
Reporter: bwiedemann(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: Development
Blocker: ---
See also https://reproducible-builds.org/
and https://reproducible-builds.org/specs/source-date-epoch/
When packages include the current time of build
it results in binaries that differ on every build
and thus trigger rebuilds of depending packages
and are published to mirrors and users
when actually nothing really changed.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=952198
Bug ID: 952198
Summary: django-admin does not work, django-admin.py does
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.1 RC1 1
Hardware: x86-64
OS: openSUSE 42.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Development
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: o.kurz(a)gmx.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
observation:
The django tutorial
https://docs.djangoproject.com/en/1.8/intro/tutorial01/
suggests to use the tool "django-admin" with django >= v1.7 which is also
available in Leap but does not work. "django-admin.py" also exists and works
ok.
steps to reproduce:
- "zypper in python-Django python-sqlite" # confirm uninstallation of blocker
package
- "django-admin startproject mysite"
- observe error with python traceback
problem:
unknown so far. Is ist maybe related that python-Django (still) uses python2?
workaround:
- Use django-admin.py which works flawlessly, e.g. example project can be
configured and run:
"django-admin.py startproject mysite && python manage.py migrate && python
manage.py runserver", connect with webbrowser to http://localhost:8000.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084017
Bug ID: 1084017
Summary: YaST in Leap 15 fails to set boot flags correctly
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.0
Hardware: x86-64
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: Larry.Finger(a)lwfinger.net
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
Created attachment 762755
--> http://bugzilla.suse.com/attachment.cgi?id=762755&action=edit
Compressed YaST2 logs
My system has a GPT partitioning scheme and does not use EFI. I also put the
boot block at the start of the active partition, and have generic boot code in
the MBR. The active partition is indicated with the legacy_boot flag.
A partial df for the system is:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 60213124 9954072 47170668 18% /
/dev/sda6 53826316 32795236 20576144 62% /var/tmp
/dev/sda7 51255784 20631016 28050216 43% /TW
/dev/sda4 60344404 22760752 36522788 39% /Leap42.3
/dev/sda5 711705020 393141448 282387980 59% /home
tmpfs 809360 20 809340 1% /run/user/1000
Looking at the partitions with parted:
GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: ATA Samsung SSD 850 (scsi)
Disk /dev/sda: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: pmbr_boot
Number Start End Size File system Name Flags
1 1049kB 9437kB 8389kB bios_grub
2 9437kB 16.8GB 16.8GB linux-swap(v1) swap
3 16.8GB 79.7GB 62.9GB ext4
4 79.7GB 143GB 62.9GB ext4 msftdata
5 143GB 883GB 741GB ext4 msftdata
6 883GB 939GB 56.1GB ext4 msftdata
8 939GB 971GB 31.5GB ext4
7 971GB 1024GB 53.5GB ext4 legacy_boot, msftdata
(parted) quit
In this case, partition number 7 will be booted. Running YaST => System => Boot
Loader changes nothing. If I want the automatic boot to choose Leap 15.0, I
need to manually toggle the legacy_boot flag on partitions 7 and 3.
Attached is a compressed copy of the /var/log/YaST2/ directory.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1027519
Bug ID: 1027519
Summary: Xen: Missing upstream bug fixes
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Xen
Assignee: xen-bugs(a)suse.de
Reporter: carnold(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
There are upstream patches fixing bugs needed for this version of Xen.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1048337
Bug ID: 1048337
Summary: yast2-slide-show need to adjust the install path for
new product builder
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: mlin(a)suse.com
QA Contact: jsrain(a)suse.com
CC: adrian(a)suse.com
Found By: ---
Blocker: ---
I've tested this in the staging project, I hot-patched yast2-slide-show then
all files are located at /usr/lib/skelcd/CD1 for new product builder, since
DATADIR is obsoleted already then new product builder doesn't have process
those files. you can find testdvd build log at
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:…
so the main question: is product builder still support slideshow? if so where
is the right path it should be?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=980292
Bug ID: 980292
Summary: Yast shouldn't allow running two instances of module
at once
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: hguo(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
It's very easy to mistakenly double click on a module icon in Yast2, causing
two instances of the module to be started, and there's absolutely no point in
using more than one instance of any yast module.
Please disallow double click on yast2, and prevent more than one instance of
module to be started.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1044803
Bug ID: 1044803
Summary: Default online repositories not used even if
installing with network connection by default
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.3
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Installation
Assignee: yast2-maintainers(a)suse.de
Reporter: opensuse.lietuviu.kalba(a)gmail.com
QA Contact: jsrain(a)suse.com
Depends on: 1044741
Found By: ---
Blocker: ---
+++ This bug was initially created as a clone of Bug #1044741 +++
I did installation from openSUSE-Leap-42.3-DVD-x86_64-Build0279-Media.iso image
and during installation there was internet connection and computer was ONLINE.
But I found that it tried to use only DVD as repository...
Though default online repositories (oss, non-oss, oss-updates, non-oss-updates)
will be added only if I intentionally pressed to configure online repositories
at dialog for computer role.
If I remember good, in previous versions these four _default_ repos where
enabled by default, and we had option to include _additional_ repositories.
See yast2logs and screenshots in bug#1044741
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=976384
Bug ID: 976384
Summary: Qt-Creator Documentation is not found out-of-the-box
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: VMWare
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: gorgoglione(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
In Qt-Creator 3.6.0, selecting Help -> Contents from menu, the following error
message is displayed:
The page could not be found
Error loading: qthelp://org.qt-project.qtcreator.360/doc/index.html
Check that you have the corresponding documentation set installed.
Probably the documentation it's not installed into the default folder and
Qt-Creator configuration was not updated to point to the right location.
The fix which worked for me was to select Tools -> Options... -> Help ->
Documentation -> Add, and select the following file:
/usr/share/doc/packages/libqt5/qtcreator.qch
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1065388
Bug ID: 1065388
Summary: apparmor is breaking tool file in lessopen.sh
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: All
OS: openSUSE Factory
Status: NEW
Severity: Major
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: werner(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Tracing lessopen.sh with
export LESS_ADVANCED_PREPROCESSOR=yes
shows
[...]
++ file -L ./less.1
+ type='./less.1: writable, regular file, no read permission'
but it should be
noether less/less-487> file -L ./less.1
./less.1: troff or preprocessor input, ASCII text
in /etc/apparmor.d/usr.bin.lessopen.sh I found
/usr/bin/file rix,
but no rule for /usr/bin/file its self!
All tools listed in /etc/apparmor.d/usr.bin.lessopen.sh should be able to
read files as otherwise nothings goes.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=972678
Bug ID: 972678
Summary: KDE:Qt/python-pyside: Bug - Installation of this
breaks software "opensesame"
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Bugzilla
Assignee: dmueller(a)suse.com
Reporter: patrickmurphy221(a)gmail.com
QA Contact: novbugzilla-bugs(a)forge.provo.novell.com
Found By: ---
Blocker: ---
- Overview
Tumbleweed zypper dup requests installation of python-pyside, but installing it
breaks the program "opensesame".
- More detail
Installed OpenSUSE Tumbleweed (snapshot 2016-03-18).
Installed package "opensesame" (psychology experiment builder, homepage:
http://osdoc.cogsci.nl/) from OpenSUSE Science repository
(https://build.opensuse.org/project/show/science). It works fine.
When I do a "zypper dup" (March 23rd or 24th), the package "python-pyside" is
installed (requested by the distribution; not a dependency of opensesame) and
it breaks opensesame. Trying to run opensesame gives this error instead of
launching the program:
python: siplib.c:8551: sip_api_can_convert_to_type: Assertion `td == ((void
*)0) || (((td)->td_flags & 0x0007) == 0x0000) || (((td)->td_flags & 0x0007) ==
0x0002)' failed.
Aborted (core dumped)
Uninstalling python-pyside makes opensesame work again (but "zypper dup"
continues to request that I install python-pyside). This does not seem to be
specific to the OpenSUSE Science repository, since downloading the opensesame
python source from its official website and running that gives the exact same
result.
- To reproduce
1. Install opensesame, from OpenSUSE Science repo or from source.
2. Install python-pyside (as requested by zypper dup).
Reversing the order has same effect. Happens on Tumbleweed. In the past I've
run opensesame on Leap without problems, but I don't think it ever requested
installation of python-pyside, so breakage would not be expected.
(First time submitting a bug; apologies if I didn't include the right detail or
use the right format.)
--
You are receiving this mail because:
You are on the CC list for the bug.